netdev - Re: [PATCH 0/2] net: atlantic: make some symbol & function static

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] [day] [month] [year] [list]

Message-Id: <20191111.220633.559233112634144943.davem@redhat.com>
Date:   Mon, 11 Nov 2019 22:06:33 -0800 (PST)
From:   David Miller <davem@...hat.com>
To:     zhengbin13@...wei.com
Cc:     irusskikh@...vell.com, netdev@...r.kernel.org
Subject: Re: [PATCH 0/2] net: atlantic: make some symbol & function static

You need to start properly marking your Subject lines with the target
tree your changes are indended to go into.

In this case, the code you are patching only exists in "net-next".

How in the world is a maintainer supposed to know this when reading
your changes?  You don't even bother providing Fixes: tags which
mark the commit that introduced the code being marked static either.