All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Sasha Levin <sashal@kernel.org>, stable <stable@vger.kernel.org>,
	Dmitry Golovin <dima@golovin.in>,
	Nathan Chancellor <natechancellor@gmail.com>,
	Sedat Dilek <sedat.dilek@gmail.com>,
	Fangrui Song <maskray@google.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Jian Cai <jiancai@google.com>,
	Manoj Gupta <manojgupta@google.com>,
	Luis Lozano <llozano@google.com>
Subject: Re: 5.4 and 4.19 warning fix for LLVM_IAS
Date: Fri, 11 Dec 2020 15:25:23 +0100	[thread overview]
Message-ID: <X9OBU+Ey8xlrFv2F@kroah.com> (raw)
In-Reply-To: <CAKwvOdkN85dnAEUCvjULh8-gojwmK-e4-aVhNbO0RdyXsO_H2w@mail.gmail.com>

On Thu, Dec 10, 2020 at 01:21:00PM -0800, Nick Desaulniers wrote:
> On Wed, Dec 9, 2020 at 2:58 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Dec 08, 2020 at 04:43:34PM -0800, Nick Desaulniers wrote:
> > > Dear stable kernel maintainers,
> > > (Woah, two in one day; have I exceeded my limit?)
> > >
> > > Please consider the attached patch for 5.4 and 4.19 for commit
> > > b8a9092330da ("Kbuild: do not emit debug info for assembly with
> > > LLVM_IAS=1"), which fixes a significant number of warnings under arch/
> > > when assembling a kernel with Clang.
> >
> > I also need a version of this for 5.9.y before we can take this for
> > older kernels.  Can you provide that as well?
> 
> Yes, apologies.  It's similar to the 5.4.y patch, but with a shorter
> set of conflicts as noted in the commit message.  Attached.
> -- 
> Thanks,
> ~Nick Desaulniers

thanks, all now applied.

greg k-h

      reply	other threads:[~2020-12-11 15:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09  0:43 5.4 and 4.19 warning fix for LLVM_IAS Nick Desaulniers
2020-12-09 10:59 ` Greg KH
2020-12-10 21:21   ` Nick Desaulniers
2020-12-11 14:25     ` 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=X9OBU+Ey8xlrFv2F@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dima@golovin.in \
    --cc=jiancai@google.com \
    --cc=llozano@google.com \
    --cc=manojgupta@google.com \
    --cc=masahiroy@kernel.org \
    --cc=maskray@google.com \
    --cc=natechancellor@gmail.com \
    --cc=ndesaulniers@google.com \
    --cc=sashal@kernel.org \
    --cc=sedat.dilek@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.