From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/ldt: Rename ldr_struct.size to .n_entries
Date: Wed, 7 Jun 2017 12:24:19 +0200 [thread overview]
Message-ID: <20170607102419.nphn7rps77eruuid@pd.tnic> (raw)
In-Reply-To: <CALCETrWEGgOaSWknQBsGED+iUv0HhFfaNoug+BWOGqSxSdCa1w@mail.gmail.com>
On Tue, Jun 06, 2017 at 03:20:22PM -0700, Andy Lutomirski wrote:
> In the subject: ldt_struct, perhaps?
Right. Committer, pls fix. :-)
> Otherwise looks good.
Thanks.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2017-06-07 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 17:31 [PATCH] x86/ldt: Rename ldr_struct.size to .n_entries Borislav Petkov
2017-06-06 22:20 ` Andy Lutomirski
2017-06-07 10:24 ` Borislav Petkov [this message]
2017-06-08 7:27 ` Ingo Molnar
2017-06-08 9:19 ` [tip:x86/mm] x86/ldt: Rename ldt_struct::size to ::nr_entries tip-bot for 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=20170607102419.nphn7rps77eruuid@pd.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--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).