mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Borislav Petkov <bp@alien8.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andy Lutomirski <luto@kernel.org>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	x86@kernel.org, David Howells <dhowells@redhat.com>,
	Len Brown <lenb@kernel.org>
Subject: Re: [PATCH] x86/asm/msr: Retract msr-index.h
Date: Thu, 4 Jun 2015 08:09:12 +0200	[thread overview]
Message-ID: <20150604060912.GA14159@gmail.com> (raw)
In-Reply-To: <556F4DE1.8070706@zytor.com>


* H. Peter Anvin <hpa@zytor.com> wrote:

> On 06/03/2015 11:21 AM, Borislav Petkov wrote:
> > On Wed, Jun 03, 2015 at 02:41:48PM +0200, Borislav Petkov wrote:
> >> This header containing all MSRs and respective bit definitions got
> >> exported to userspace in conjunction with the big uapi shuffle.
> >>
> >> But, it doesn't have anything to do in the uapi headers because
> >> userspace can do its own MSR defines and exporting them from the
> >> kernel blocks us from doing cleanups/renames in that header. Which is
> >> ridiculous - it is not kernel's job to export such a header and keep
> >> MSRs list and their names stable.
> > 
> > Here's v2. Needed to *not* include it into uapi/asm/msr.h either.
> 
> I really like the patch, but the description is awful.
> 
> How about: "x86/uapi: <asm/msr.h> is not a UAPI"

So a small nit: a simple statement of fact is not really a proper commit title.
A commit title should express what the patch _does_.

Missing leading verbs are really passive-aggressive on the reader of a flow of 
commit titles - such as when reading a short log or a one-line git log.

Something like:

	x86/uapi: Remove <asm/msr.h> from the list of exported UAPI headers

or so would work fine with me.

Thanks!

	Ingo

  parent reply	other threads:[~2015-06-04  6:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 12:41 Borislav Petkov
2015-06-03 18:21 ` Borislav Petkov
2015-06-03 18:56   ` H. Peter Anvin
2015-06-03 20:06     ` Borislav Petkov
2015-06-03 21:23       ` H. Peter Anvin
2015-06-04  6:09     ` Ingo Molnar [this message]
2015-06-04  7:59       ` Borislav Petkov
2015-06-04 12:45         ` Ingo Molnar
2015-07-16  0:39   ` Len Brown

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=20150604060912.GA14159@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=dhowells@redhat.com \
    --cc=hpa@zytor.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=peterz@infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome