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: <1cb8dd94-a71b-aa91-3bed-365ce081dfd6@redhat.com>
Date:   Thu, 12 Aug 2021 09:40:21 +0200
From:   Hans de Goede <hdegoede@...hat.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Mark Gross <mark.gross@...el.com>
Cc:     Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the drivers-x86 tree

Hi,

On 8/11/21 12:16 AM, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   5c62c3d98b87 ("platform/x86: ISST: Fix optimization with use of numa")
> 
> Fixes tag
> 
>   Fixes: aa2ddd242572 ("ISST: Use numa node id for cpu pci dev mapping")
> 
> has these problem(s):
> 
>   - Subject does not match target commit subject
>     Just use
> 	git log -1 --format='Fixes: %h ("%s")'

Thanks, I've fixes this now and then a forced-push of the pdx86 for-next branch.

Question, is there some script which I can run on my own tree to catch
this (and similar issues) myself?  checkpatch does not catch this problem.

Regards,

Hans

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ