[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180121093741.GA5010@kroah.com>
Date: Sun, 21 Jan 2018 10:37:41 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Gabriel C <nix.or.die@...il.com>,
Laura Abbott <labbott@...hat.com>,
Ingo Molnar <mingo@...nel.org>,
Tom Lendacky <thomas.lendacky@....com>,
Borislav Petkov <bp@...e.de>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Brijesh Singh <brijesh.singh@....com>, X86 ML <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
stable <stable@...r.kernel.org>
Subject: Re: [PATCH] x86: Use __nostackprotect for sme_encrypt_kernel
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@...il.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
Powered by blists - more mailing lists