From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Gabriel C <nix.or.die@gmail.com>,
Laura Abbott <labbott@redhat.com>, Ingo Molnar <mingo@kernel.org>,
Tom Lendacky <thomas.lendacky@amd.com>,
Borislav Petkov <bp@suse.de>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Brijesh Singh <brijesh.singh@amd.com>, X86 ML <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] x86: Use __nostackprotect for sme_encrypt_kernel
Date: Sun, 21 Jan 2018 10:37:41 +0100 [thread overview]
Message-ID: <20180121093741.GA5010@kroah.com> (raw)
In-Reply-To: <CA+55aFxZshQJweUz4cDeSap9cqCL5RB55BmcGqsBs3=ZOJpeGw@mail.gmail.com>
On Sat, Jan 20, 2018 at 08:16:31PM -0800, Linus Torvalds wrote:
> On Sat, Jan 20, 2018 at 5:49 PM, Gabriel C <nix.or.die@gmail.com> wrote:
> >
> > Added stable to CC since the patch series this patch fixes
> > is in stable-queue.
>
> Oh, it wasn't clear from the commit message. But I guess the "Fixes:"
> tag would have caught Greg's eye regardless.
Ugh, I am _so_ behind in looking at patches that only have a Fixes: tag
in it and not a "Cc: stable@" tag, due to the recent high-volume of the
latter.
But they will end up in a mbox that I need to dig out of eventually, but
it will take time, so if you know you want a patch in a stable release,
it's much easier to just use the "Cc: stable@" tag please.
thanks,
greg k-h
next prev parent reply other threads:[~2018-01-21 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b7a8e990-9d1d-39b2-671d-a44d5647dbec@amd.com>
[not found] ` <20180121011402.9557-1-labbott@redhat.com>
[not found] ` <CA+55aFz+gy50ZqrZm=L5oU3qgC8QTtEyXN+NjnqOKfqZxU1f8w@mail.gmail.com>
2018-01-21 1:49 ` [PATCH] x86: Use __nostackprotect for sme_encrypt_kernel Gabriel C
2018-01-21 4:16 ` Linus Torvalds
2018-01-21 9:37 ` Greg Kroah-Hartman [this message]
2018-01-21 9:50 ` Ingo Molnar
2018-01-21 10:36 ` Greg Kroah-Hartman
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=20180121093741.GA5010@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bp@suse.de \
--cc=brijesh.singh@amd.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nix.or.die@gmail.com \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@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).