On 11/24/20 9:15 PM, Jakub Kicinski wrote: > Make an explicit suggestion how to post user space side of kernel > patches to avoid reposts when patchwork groups the wrong patches. > > v2: mention the cases unlike iproute2 explicitly > > Signed-off-by: Jakub Kicinski <k...@kernel.org> > Reviewed-by: Florian Fainelli <f.faine...@gmail.com> > --- > Documentation/networking/netdev-FAQ.rst | 26 +++++++++++++++++++++++++ > 1 file changed, 26 insertions(+) > > diff --git a/Documentation/networking/netdev-FAQ.rst > b/Documentation/networking/netdev-FAQ.rst > index 21537766be4d..4b9ed5874d5a 100644 > --- a/Documentation/networking/netdev-FAQ.rst > +++ b/Documentation/networking/netdev-FAQ.rst > @@ -254,6 +254,32 @@ you will have done run-time testing specific to your > change, but at a > minimum, your changes should survive an ``allyesconfig`` and an > ``allmodconfig`` build without new warnings or failures. > > +Q: How do I post corresponding changes to user space components? > +---------------------------------------------------------------- > +A: User space code exercising kernel features should be posted > +alongside kernel patches. This gives reviewers a chance to see > +how any new interface is used and how well it works. > + > +When user space tools reside in the kernel repo itself all changes > +should generally come as one series. If series becomes too large > +or the user space project is not reviewed on netdev include a link > +to a public repo where user space patches can be seen. > + > +In case user space tooling lives in a separate repository but is > +reviewed on netdev (e.g. patches to `iproute2` tools) kernel and
double space. besides that: Reviewed-by: David Ahern <dsah...@kernel.org>
