linux-kernel - Re: linux-next: Fixes tag needs some work in the pinctrl-intel-fixes tree

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 for Android: free password hash cracker in your pocket

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

Date:   Tue, 1 Oct 2019 17:43:35 +0300
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Mika Westerberg <mika.westerberg@...ux.intel.com>
Subject: Re: linux-next: Fixes tag needs some work in the pinctrl-intel-fixes tree

On Tue, Oct 1, 2019 at 5:32 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> In commit
>
>   d21556b6ff04 ("pinctrl: intel: Allocate IRQ chip dynamic")
>
> Fixes tag
>
>   Fixes: ee1a6ca43dba ("Add Intel Broxton pin controller support")
>
> has these problem(s):
>
>   - Subject does not match target commit subject
>     Just use
>         git log -1 --format='Fixes: %h ("%s")'

Thank you for pointing this out.
Nevertheless I have a question. Does prefix carry crucial information
for the commits which are already in the kernel? Can't we simple use
substring (or let's say most meaningful part of the commit subject)
instead?

-- 
With Best Regards,
Andy Shevchenko