From: Borislav Petkov <bp@alien8.de>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: "Nathan Chancellor" <natechancellor@gmail.com>,
"Nirav Davé" <niravd@google.com>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] x86/boot: clean up headers
Date: Tue, 5 Mar 2019 09:57:07 +0100 [thread overview]
Message-ID: <20190305085707.GA8256@zn.tnic> (raw)
In-Reply-To: <CAKwvOdmCnwcUCNT0q=+g9sjTdg_tv3WMC6wWyOhkzDPqFMUhbA@mail.gmail.com>
On Mon, Mar 04, 2019 at 04:15:49PM -0800, Nick Desaulniers wrote:
> Well, should have cut that out of the commit message too in V3...sigh.
> Boris assuming everyone's ok with this patch; can you just drop this
> sentence from the commit message should you apply the patch (or shall
> I send a v4)?
I'll take a look once the merge window is over and all the dust settles.
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-03-05 8:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 0:07 [PATCH] x86/boot: clean up headers Nick Desaulniers
2019-03-02 0:13 ` Nathan Chancellor
2019-03-02 2:27 ` Stephen Rothwell
2019-03-02 2:30 ` Stephen Rothwell
2019-03-04 17:50 ` [PATCH v2] " Nick Desaulniers
2019-03-04 22:51 ` Stephen Rothwell
2019-03-05 0:12 ` [PATCH v3] " Nick Desaulniers
2019-03-05 0:15 ` Nick Desaulniers
2019-03-05 8:57 ` Borislav Petkov [this message]
2019-03-14 22:14 ` [PATCH v4] " Nick Desaulniers
2019-03-21 11:28 ` [tip:x86/urgent] x86/boot: Restrict header scope to make Clang happy tip-bot for Nick Desaulniers
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=20190305085707.GA8256@zn.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=niravd@google.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.