stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Sasha Levin <sashal@kernel.org>,
	"# 3.4.x" <stable@vger.kernel.org>,
	Lucas Henneman <henneman@google.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>,
	Nathan Chancellor <nathan@kernel.org>,
	Will Deacon <will@kernel.org>,
	llvm@lists.linux.dev, Pavel Machek <pavel@denx.de>
Subject: Re: backport of 14831fad73f5 for 5.10 and 5.4
Date: Mon, 22 Nov 2021 12:15:34 +0100	[thread overview]
Message-ID: <YZt71oaVVAzhNrG+@kroah.com> (raw)
In-Reply-To: <CAKwvOdkZ1ydLs2VwvVLtT7QK+e1gNB0ZE5RqTxMY15QQvhxZ1w@mail.gmail.com>

On Fri, Nov 19, 2021 at 02:29:09PM -0800, Nick Desaulniers wrote:
> On Fri, Nov 19, 2021 at 5:30 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Thu, Nov 18, 2021 at 11:30:38AM -0800, Nick Desaulniers wrote:
> > > Dear stable kernel maintainers,
> > > Please consider applying the attached backport of 14831fad73f5 to
> > > linux-5.10.y and linux-5.4.y.
> > >
> > > 14831fad73f5 first landed in v5.16-rc1.
> > >
> > > There was a minor conflict due to missing e35123d83ee3 ("arm64: lto:
> > > Strengthen READ_ONCE() to acquire when CONFIG_LTO=y") which first
> > > landed in v5.11-rc1.
> > >
> > > It fixes a minor warning observed during `make mrproper` for Android
> > > kernel builds.
> >
> > Now queued up, thanks.
> 
> I'm sorry; I made a mistake.  As reported by Pavel in
> https://lore.kernel.org/stable/20211119214713.GB23353@amd/
> I missed part of the backport.  Attached is a v2.
> -- 
> Thanks,
> ~Nick Desaulniers



Now queued up, thnaks.

greg k-h

      reply	other threads:[~2021-11-22 11:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 19:30 backport of 14831fad73f5 for 5.10 and 5.4 Nick Desaulniers
2021-11-19 13:30 ` Greg KH
2021-11-19 22:29   ` Nick Desaulniers
2021-11-22 11:15     ` Greg KH [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=YZt71oaVVAzhNrG+@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=henneman@google.com \
    --cc=llvm@lists.linux.dev \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=pavel@denx.de \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=vincenzo.frascino@arm.com \
    --cc=will@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;
as well as URLs for NNTP newsgroup(s).