Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
	"# 3.4.x" <stable@vger.kernel.org>,
	Jiri Slaby <jirislaby@kernel.org>,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	Borislav Petkov <bp@suse.de>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Alistair Delva <adelva@google.com>
Subject: Re: 78762b0e79bc for linux-5.4.y
Date: Fri, 15 Jan 2021 10:33:11 +0100	[thread overview]
Message-ID: <YAFhV8w2Ynl8oYBz@kroah.com> (raw)
In-Reply-To: <20210113175107.GT4035784@sasha-vm>

On Wed, Jan 13, 2021 at 12:51:07PM -0500, Sasha Levin wrote:
> On Mon, Jan 11, 2021 at 03:41:37PM -0800, Nick Desaulniers wrote:
> > Please consider applying the following patch for LLVM_IAS=1 support
> > for Android's i386 cuttlefish virtual device:
> > commit 78762b0e79bc ("x86/asm/32: Add ENDs to some functions and
> > relabel with SYM_CODE_*")
> > which first landed in v5.5-rc1.
> > 
> > There was a small conflict in arch/x86/xen/xen-asm_32.S due to the
> > order of backports that was trivial to resolve.  You can see the list
> > of commits to it in linux-5.7.y:
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/arch/x86/xen/xen-asm_32.S?h=linux-5.7.y
> > as arch/x86/xen/xen-asm_32.S was removed in
> > commit a13f2ef168cb ("x86/xen: remove 32-bit Xen PV guest support") in v5.9-rc1.
> 
> Queued up, thanks!

You stripped out the "commit XXX upstream" line from the patch :(

I've fixed that up now.

thanks,

greg k-h

      reply	other threads:[~2021-01-15  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 23:41 78762b0e79bc for linux-5.4.y Nick Desaulniers
2021-01-13 17:51 ` Sasha Levin
2021-01-15  9:33   ` 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=YAFhV8w2Ynl8oYBz@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=adelva@google.com \
    --cc=bp@suse.de \
    --cc=clang-built-linux@googlegroups.com \
    --cc=jirislaby@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=sashal@kernel.org \
    --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