netdev - Re: [PATCH net v2] Documentation: netdev-FAQ: suggest how to post co-dependent series

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 24 Nov 2020 21:38:56 -0700
From:   David Ahern <dsahern@...il.com>
To:     Jakub Kicinski <kuba@...nel.org>, davem@...emloft.net
Cc:     netdev@...r.kernel.org, brouer@...hat.com, f.fainelli@...il.com,
        andrea.mayer@...roma2.it, stephen@...workplumber.org,
        ast@...nel.org
Subject: Re: [PATCH net v2] Documentation: netdev-FAQ: suggest how to post
 co-dependent series

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 <kuba@...nel.org>
> Reviewed-by: Florian Fainelli <f.fainelli@...il.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 <dsahern@...nel.org>