linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
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 13:05:39 +0100	[thread overview]
Message-ID: <CAMj1kXHkvwr9=+AwNnxfMy8EosUgj1Hsp=g2YqqhwqQRsyauGA@mail.gmail.com> (raw)
In-Reply-To: <20201208120355.GQ1551@shell.armlinux.org.uk>

On Tue, 8 Dec 2020 at 13:04, Russell King - ARM Linux admin
<linux@armlinux.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@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.
>

OK, thanks.

      reply	other threads:[~2020-12-08 12:06 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
2020-12-08 12:05     ` Ard Biesheuvel [this message]

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='CAMj1kXHkvwr9=+AwNnxfMy8EosUgj1Hsp=g2YqqhwqQRsyauGA@mail.gmail.com' \
    --to=ardb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).