linux-kernel - Re: linux-next: Fixes tag needs some work in the arm 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Tue, 8 Dec 2020 13:05:39 +0100
From:   Ard Biesheuvel <ardb@...nel.org>
To:     Russell King - ARM Linux admin <linux@...linux.org.uk>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        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 arm tree

On Tue, 8 Dec 2020 at 13:04, Russell King - ARM Linux admin
<linux@...linux.org.uk> wrote:
>
> On Tue, Dec 08, 2020 at 01:02:05PM +0100, Ard Biesheuvel wrote:
> > On Tue, 8 Dec 2020 at 12:39, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > >
> > > Hi all,
> > >
> > > In commit
> > >
> > >   4812d516af55 ("ARM: 9027/1: head.S: explicitly map DT even if it lives in the first physical section")
> > >
> > > Fixes tag
> > >
> > >   Fixes: 149a3ffe62b9dbc3 ("9012/1: move device tree mapping out of linear region")
> > >
> > > has these problem(s):
> > >
> > >   - Target SHA1 does not exist
> > >
> > > Maybe you meant
> > >
> > > Fixes: 7a1be318f579 ("ARM: 9012/1: move device tree mapping out of linear region")
> > >
> >
> > Oops, my bad.
> >
> > I think we can drop the Fixes tag entirely - I added it to the patch
> > when I sent it to the mailing list because it fixes a patch that had
> > already been queued up by Russell at that point. However, I don't
> > think it is that important to capture this relation in the future,
> > given that they will all end up in the same mainline -rc
>
> I've already dropped it and fixed the SHA1 reference in the commit
> message.
>

OK, thanks.