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
10 Documentation/process/submitting-patches.rst. This document only describes
44 Submitting patches
49 A: BPF CI is GitHub based and hosted at https://github.com/kernel-patches/bpf.
53 The following steps lay out how to start a CI run for your patches:
59 or bpf branch, and apply your to-be-tested patches on top of it
62 kernel-patches/bpf's bpf-next_base or bpf_base branch, respectively
65 that capacity is shared with patches submitted upstream being checked and so
69 updated as patches are pushed to the respective upstream branches they track. As
74 Q: To which mailing list do I need to submit my BPF patches?
76 A: Please submit your BPF patches to the bpf kernel mailing list:
83 the changes and provide their Acked-by's to the patches.
85 Q: Where can I find patches currently under discussion for BPF subsystem?
87 A: All patches that are Cc'ed to netdev are queued for review under netdev
92 Those patches which target BPF, are assigned to a 'bpf' delegate for
94 patches under review can be found at:
98 Once the patches have been reviewed by the BPF community as a whole
101 means that the patches look good from a BPF perspective and have been
104 In case feedback from the community requires a respin of the patches,
106 from the current review queue. Likewise for cases where patches would
112 A: There are two BPF kernel trees (git repositories). Once patches have
123 which branch patches should get rebased to.
125 Accumulated BPF patches in the bpf tree will regularly get pulled
126 into the net kernel tree. Likewise, accumulated BPF patches accepted
136 to other trees (e.g. tracing) with a small subset of the patches, but
140 patches and can be searched on netdev kernel mailing list through the
169 the patches.
171 If it is clear that patches should go into bpf or bpf-next tree,
172 please make sure to rebase the patches against those trees in
200 i) accumulate and stage BPF patches for integration into trees
204 workloads on the patches before they make their way any further.
207 the patches end up in net or net-next tree, respectively, and
212 Q: How long do I need to wait for feedback on my BPF patches?
222 accumulate too many patches in bpf or bpf-next.
229 Q: Are patches applied to bpf-next when the merge window is open?
301 Q: Do you accept patches as well for iproute2's BPF loader?
307 While those patches are not processed by the BPF kernel maintainers,
315 The patches need to have a subject prefix of '``[PATCH iproute2
324 Like BPF, the patches end up in patchwork under the netdev project and
329 Q: What is the minimum requirement before I submit my BPF patches?
331 A: When submitting patches, always take the time and properly test your
332 patches *prior* to submission. Never rush them! If maintainers find
333 that your patches have not been properly tested, it is a good way to
342 We also don't accept patches with an empty commit message. Take your
416 ask the BPF maintainers to queue the patches instead. This can be done
421 Q: Queue stable patches
423 Q: Where do I find currently queued BPF patches that will be submitted
426 A: Once patches that fix critical bugs got applied into the bpf tree, they
434 After having been under broader exposure, the queued patches will be
437 Testing patches