Lines Matching refs:patches

6 workflows related to reporting bugs, submitting patches, and queueing
7 patches for stable kernels.
9 For general information about submitting patches, please refer to
44 Submitting patches
47 Q: To which mailing list do I need to submit my BPF patches?
49 A: Please submit your BPF patches to the bpf kernel mailing list:
56 the changes and provide their Acked-by's to the patches.
58 Q: Where can I find patches currently under discussion for BPF subsystem?
60 A: All patches that are Cc'ed to netdev are queued for review under netdev
65 Those patches which target BPF, are assigned to a 'bpf' delegate for
67 patches under review can be found at:
71 Once the patches have been reviewed by the BPF community as a whole
74 means that the patches look good from a BPF perspective and have been
77 In case feedback from the community requires a respin of the patches,
79 from the current review queue. Likewise for cases where patches would
85 A: There are two BPF kernel trees (git repositories). Once patches have
96 which branch patches should get rebased to.
98 Accumulated BPF patches in the bpf tree will regularly get pulled
99 into the net kernel tree. Likewise, accumulated BPF patches accepted
109 to other trees (e.g. tracing) with a small subset of the patches, but
113 patches and can be searched on netdev kernel mailing list through the
142 the patches.
144 If it is clear that patches should go into bpf or bpf-next tree,
145 please make sure to rebase the patches against those trees in
173 i) accumulate and stage BPF patches for integration into trees
177 workloads on the patches before they make their way any further.
180 the patches end up in net or net-next tree, respectively, and
185 Q: How long do I need to wait for feedback on my BPF patches?
195 accumulate too many patches in bpf or bpf-next.
202 Q: Are patches applied to bpf-next when the merge window is open?
274 Q: Do you accept patches as well for iproute2's BPF loader?
280 While those patches are not processed by the BPF kernel maintainers,
288 The patches need to have a subject prefix of '``[PATCH iproute2
297 Like BPF, the patches end up in patchwork under the netdev project and
302 Q: What is the minimum requirement before I submit my BPF patches?
304 A: When submitting patches, always take the time and properly test your
305 patches *prior* to submission. Never rush them! If maintainers find
306 that your patches have not been properly tested, it is a good way to
315 We also don't accept patches with an empty commit message. Take your
389 ask the BPF maintainers to queue the patches instead. This can be done
394 Q: Queue stable patches
396 Q: Where do I find currently queued BPF patches that will be submitted
399 A: Once patches that fix critical bugs got applied into the bpf tree, they
407 After having been under broader exposure, the queued patches will be
410 Testing patches