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:   Mon, 20 May 2019 13:16:23 +0000
From:   Michal Kalderon <mkalderon@...vell.com>
To:     Joe Perches <joe@...ches.com>, "leon@...nel.org" <leon@...nel.org>,
        "apw@...onical.com" <apw@...onical.com>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "David Miller" <davem@...emloft.net>
Subject: RE: [EXT] Re: [PATCH] checkpatch: add test for empty line after Fixes
 statement

> From: Joe Perches <joe@...ches.com>
> Sent: Monday, May 20, 2019 3:57 PM
> Subject: [EXT] Re: [PATCH] checkpatch: add test for empty line after Fixes
> statement
> 
> External Email
> 
> ----------------------------------------------------------------------
> On Mon, 2019-05-20 at 15:42 +0300, Michal Kalderon wrote:
> > Check that there is no empty line after a fixes statement
> 
> why?
> 
This comment is given a lot on the netdev and rdma mailing lists when patches are submitted with
an empty line between Fixes: tag and SOB tags. Since "Fixes:" is just another tag and should be kept
together with the other ones.
thanks,
Michal

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ