public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <andi@firstfloor.org>, Andi Kleen <ak@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 1/3] x86: Readd asmregparm
Date: Wed, 8 Jun 2011 10:53:55 +0200	[thread overview]
Message-ID: <20110608085355.GA1692@elte.hu> (raw)
In-Reply-To: <20110608083750.GH27166@one.firstfloor.org>


* Andi Kleen <andi@firstfloor.org> wrote:

> > That's a totally useless changelog (you are deliberately hiding 
> > information again) so the series is obviously not acceptable.
> > Please fix and resend.
> 
> I reread it and it seems complete to me. Please be more specific.
> 
> If you refer to the followon patchkit - it's not ready for posting 
> yet. [...]

You contradict yourself here - why do you claim that it's "complete" 
while you readily admit in the *next* sentence that the "followon 
patchkit" (with no specifics provided whatsoever) is "not ready for 
posting yet"?

You are not a newbie anymore, you know what the rules are for 
*everyone*: if it's not ready for posting yet then don't send a 
half-done series for inclusion, wasting everyone's time.

> [...] However I believe these changes are reasonable cleanups that 
> are useful on their own. That's why I posted them now.

Uhm, that's trivially untrue crazy talk and you should know it: the 
patches add code and typing complexity for no good stated reason 
whatsoever.

If we want the maintenance overhead of that then you better come up 
with your deliberately kept secret "project" and we'll be able to 
weigh whether the benefits overweigh the maintenance costs ...

In any case, i'd like to warn you that you are very close to me 
starting to ignore your mails summarily due to absymal low quality: 
in the past few months 70-80% of the cases your first patch 
submissions were trivially flawed, and in many cases you should have 
been well aware of the fact that they were trivially flawed. And 
that's not from a newbie but from a long-time kernel contributor!

Thanks,

	Ingo

  reply	other threads:[~2011-06-08  8:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08  1:09 [PATCH 1/3] x86: Readd asmregparm Andi Kleen
2011-06-08  1:10 ` [PATCH 2/3] x86: Add missing asmlinkages/asmregparm Andi Kleen
2011-06-08  1:10 ` [PATCH 3/3] x86: Change dotraplinkage into asmregparm for 32bit Andi Kleen
2011-06-08  8:19 ` [PATCH 1/3] x86: Readd asmregparm Ingo Molnar
2011-06-08  8:37   ` Andi Kleen
2011-06-08  8:53     ` Ingo Molnar [this message]
2011-06-08 11:57     ` Pekka Enberg
2011-06-08 12:28       ` Christoph Lameter
2011-06-08 16:01       ` Andi Kleen

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=20110608085355.GA1692@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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