From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the arm tree
Date: Tue, 8 Dec 2020 12:03:55 +0000 [thread overview]
Message-ID: <20201208120355.GQ1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAMj1kXHmQV+CCMS7HAnZP-4U=j3jSq83tvX+2O9ke8biJUcCvg@mail.gmail.com>
On Tue, Dec 08, 2020 at 01:02:05PM +0100, Ard Biesheuvel wrote:
> On Tue, 8 Dec 2020 at 12:39, Stephen Rothwell <sfr@canb.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.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2020-12-08 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 11:39 linux-next: Fixes tag needs some work in the arm tree Stephen Rothwell
2020-12-08 12:02 ` Ard Biesheuvel
2020-12-08 12:03 ` Russell King - ARM Linux admin [this message]
2020-12-08 12:05 ` Ard Biesheuvel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201208120355.GQ1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=ardb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox