public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: gregkh <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Claudiu Beznea <claudiu.beznea@microchip.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	"# 3.4.x" <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] drivers: soc: atmel: add null entry at the end of" failed to apply to 5.4-stable tree
Date: Mon, 1 Mar 2021 12:15:43 +0100	[thread overview]
Message-ID: <YDzM32cs/ZLoUYLj@kroah.com> (raw)
In-Reply-To: <CAK8P3a27HB89omfNGBWbbztB6Fg1qfOzjqtKJ7sDurMRi4AAPg@mail.gmail.com>

On Mon, Mar 01, 2021 at 11:52:17AM +0100, Arnd Bergmann wrote:
> On Mon, Mar 1, 2021 at 11:32 AM <gregkh@linuxfoundation.org> wrote:
> >
> >
> > The patch below does not apply to the 5.4-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> 
> > Fixes: caab13b49604 ("drivers: soc: atmel: Avoid calling at91_soc_init on non AT91 SoCs")
> > Cc: stable@vger.kernel.org #4.12+
> 
> Hi Greg,
> 
> Did you add a backport of the caab13b49604 patch to 5.4 and earlier?

Yes, it is in the following releases:
	4.14.219 4.19.173 5.4.95 5.10.13 5.11

> Without that patch, this one will not apply, but if you did apply caab13b49604,
> we need this one as well, and should do a backport.

Agreed, that's why I asked for one :)

thanks,

greg k-h

      reply	other threads:[~2021-03-01 11:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 10:32 FAILED: patch "[PATCH] drivers: soc: atmel: add null entry at the end of" failed to apply to 5.4-stable tree gregkh
2021-03-01 10:52 ` Arnd Bergmann
2021-03-01 11:15   ` gregkh [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=YDzM32cs/ZLoUYLj@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=claudiu.beznea@microchip.com \
    --cc=nicolas.ferre@microchip.com \
    --cc=stable@vger.kernel.org \
    /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