public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	"H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: [PATCH] x86_64: use -mskip-rax-setup when available
Date: Thu, 23 Apr 2015 14:55:02 +0200	[thread overview]
Message-ID: <871tjbm2c9.fsf@rasmusvillemoes.dk> (raw)
In-Reply-To: <20150423122959.GG28327@pd.tnic> (Borislav Petkov's message of "Thu, 23 Apr 2015 14:29:59 +0200")

On Thu, Apr 23 2015, Borislav Petkov <bp@alien8.de> wrote:

> On Thu, Apr 23, 2015 at 01:00:26PM +0200, Rasmus Villemoes wrote:
>> > or you want attribution or ...?
>> 
>> That would be nice.
>
> I fail to see for what - I see H.J. Lu's patch from Dec. 2014 and you
> repeating the same patch months later.

I think we're talking past each other. What I'd like credit for is
coming up with the idea of omitting the xor %eax,%eax in the first place
(the original mail was sent to x86@kernel.org [cc'ed to a few x86
maintainers], but that doesn't seem to be publicly archived).

So it is very much not about (attribution for) the Makefile patch itself.

> [...] it is his patch which should go because it was the first. It is
> only fair this way IMO.

Agreed - all I ask for is being mentioned somewhere in the commit
log. Again, I only sent the April 20 patch because I hadn't seen
anything happen since December.

Rasmus


  reply	other threads:[~2015-04-23 12:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 12:28 [PATCH] x86_64: use -mskip-rax-setup when available Rasmus Villemoes
2015-04-20 15:07 ` Borislav Petkov
2015-04-20 20:24   ` Rasmus Villemoes
2015-04-20 20:41     ` Borislav Petkov
2015-04-23 11:00       ` Rasmus Villemoes
2015-04-23 12:29         ` Borislav Petkov
2015-04-23 12:55           ` Rasmus Villemoes [this message]
2015-04-23 13:12             ` Borislav Petkov
2015-04-23 12:55           ` H.J. Lu

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=871tjbm2c9.fsf@rasmusvillemoes.dk \
    --to=linux@rasmusvillemoes.dk \
    --cc=bp@alien8.de \
    --cc=hjl.tools@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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