From: Greg KH <gregkh@linuxfoundation.org>
To: Andy Lutomirski <luto@kernel.org>
Cc: alexander.levin@microsoft.com,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Borislav Petkov <bp@alien8.de>, Brian Gerst <brgerst@gmail.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>, Juergen Gross <jgross@suse.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Thomas Garnier <thgarnie@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
stable <stable@vger.kernel.org>,
stable-commits@vger.kernel.org
Subject: Re: Patch "x86/boot/32: Defer resyncing initial_page_table until per-cpu is set up" has been added to the 4.9-stable tree
Date: Mon, 19 Mar 2018 10:22:39 +0100 [thread overview]
Message-ID: <20180319092239.GA29372@kroah.com> (raw)
In-Reply-To: <CALCETrXcDBcooftBbTrgZR26jgfHPsubST=0C7G07UqdX5qHsA@mail.gmail.com>
On Sun, Mar 18, 2018 at 04:36:09PM +0000, Andy Lutomirski wrote:
> On Mar 18, 2018, at 9:06 AM, <gregkh@linuxfoundation.org>
> <gregkh@linuxfoundation.org> wrote:
>
>
> This is a note to let you know that I've just added the patch titled
>
> x86/boot/32: Defer resyncing initial_page_table until per-cpu is set up
>
>
> Please make sure you get “x86/boot/32: Fix UP boot on Quark and
> possibly other platforms” too. Sorry, the fixes tag is missing.
Thanks for the info, that patch is now queued up.
greg k-h
prev parent reply other threads:[~2018-03-19 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 16:06 Patch "x86/boot/32: Defer resyncing initial_page_table until per-cpu is set up" has been added to the 4.9-stable tree gregkh
2018-03-18 16:36 ` Andy Lutomirski
2018-03-19 9:22 ` 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=20180319092239.GA29372@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.levin@microsoft.com \
--cc=ard.biesheuvel@linaro.org \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jpoimboe@redhat.com \
--cc=luto@kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.com \
--cc=torvalds@linux-foundation.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).