From: Borislav Petkov <bp@suse.de>
To: Sasha Levin <sashal@kernel.org>
Cc: Jiri Kosina <jikos@kernel.org>,
gregkh@linuxfoundation.org, aarcange@redhat.com,
ak@linux.intel.com, casey.schaufler@intel.com, dwmw@amazon.co.uk,
jpoimboe@redhat.com, peterz@infradead.org,
Thomas Gleixner <tglx@linutronix.de>,
tim.c.chen@linux.intel.com, Borislav Petkov <bpetkov@suse.de>,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] x86/speculation: Enable cross-hyperthread spectre v2 STIBP" failed to apply to 4.4-stable tree
Date: Sat, 17 Nov 2018 17:20:52 +0100 [thread overview]
Message-ID: <20181117162052.GA5065@zn.tnic> (raw)
In-Reply-To: <20181117145052.GR1706@sasha-vm>
On Sat, Nov 17, 2018 at 09:50:52AM -0500, Sasha Levin wrote:
> > http://kernel.suse.com/cgit/kernel/commit/?h=SLE12-SP3&id=f0d6957cb012ef72c9628511a75be40083865dd9
> > http://kernel.suse.com/cgit/kernel/commit/?h=SLE12-SP3&id=8b222bcb27ae6a628aa2dad5050e1d5dcbbbcecb
> > http://kernel.suse.com/cgit/kernel/commit/?h=SLE12-SP3&id=f04ca7131a830e8be2cf0742bed0a15533c35a93
>
> Boris,
>
> Can I get your Signed-off-by on these 3 backported commits?
If you click on the respective suse-commit link, for example:
suse-commit: a0dce2e59b0edd366a0d7f1ece099d94496385ba
for the first one, you'll see my Acked-by:
You probably should use those anyway as they have header and commit
message and so on...
HTH.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2018-11-17 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-10 18:37 FAILED: patch "[PATCH] x86/speculation: Enable cross-hyperthread spectre v2 STIBP" failed to apply to 4.4-stable tree gregkh
2018-11-10 20:47 ` Jiri Kosina
2018-11-17 14:50 ` Sasha Levin
2018-11-17 16:20 ` Borislav Petkov [this message]
2018-11-19 10:49 ` Borislav Petkov
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=20181117162052.GA5065@zn.tnic \
--to=bp@suse.de \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=bpetkov@suse.de \
--cc=casey.schaufler@intel.com \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=peterz@infradead.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
/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