netdev - Re: [PATCH 1/2] qed: Replace memset with eth_zero

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]

Message-Id: <20170115.233830.123911280062970298.davem@davemloft.net>
Date:   Sun, 15 Jan 2017 23:38:30 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     mayhs11saini@...il.com
Cc:     Yuval.Mintz@...ium.com, Ariel.Elior@...ium.com,
        everest-linux-l2@...ium.com, netdev@...r.kernel.org
Subject: Re: [PATCH 1/2] qed: Replace memset with eth_zero_addr

Please do not ever submit two patches which have the same exact commit
header line, as these two patches do.

When someone looks into the shortlog of GIT history all they will see
is "qed: Replace memset with eth_zero_addr" twice.

This gives the reader no idea what might be different between those
two changes.

Therefore you must give unique a commit header text for each change,
which communicates sufficiently what is different in each change.