public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Andi Kleen <ak@suse.de>,
	discuss@x86-64.org, torvalds@osdl.org, akpm@osdl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: [PATCH] [6/6] i386: Move CONFIG_DOUBLEFAULT into arch/i386 where it belongs.
Date: Thu, 20 Apr 2006 13:49:46 +0200	[thread overview]
Message-ID: <20060420114946.GM25047@stusta.de> (raw)
In-Reply-To: <20060418190839.3fa53a0f.rdunlap@xenotime.net>

On Tue, Apr 18, 2006 at 07:08:39PM -0700, Randy.Dunlap wrote:
> On Tue, 18 Apr 2006 22:12:13 +0200 Andi Kleen wrote:
> 
> > On Tuesday 18 April 2006 21:05, Adrian Bunk wrote:
> > > On Tue, Apr 18, 2006 at 12:35:22PM +0200, Andi Kleen wrote:
> > > > 
> > > > Signed-off-by: Andi Kleen <ak@suse.de>
> > > >...
> > > 
> > > NAK.
> > >  submitting a patch that is the revert of a patch that went 
> > > into Linus' tree just 8 days ago [1], I'd expect at least:
> > > - a Cc to the people involved with the patch you are reverting
> > > - a note that you are reverting a recent patch in your patch
> > >   description
> > > - an explanation why you disagree with the patch you are reverting
> > 
> > The subject was very clear. i386 options belong into arch/i386.
> 
> Yes, the timing could have been better.  Whatever.
> 
> I agree with Andi that it should be moved back to the ix86 Processor
> menu, but not where he moved it to.  My patch is below.
>...

I'd still disagree with Andi regarding this point (but it's not a very 
important issue).

My main problem with his patch is still the way he did it - sending a 
patch reverting a recently included patch with neither discussion before 
the patch nor mentioning in the patch that it's a revert nor a Cc to the 
people involved with the patch.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-04-20 11:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-18 10:35 [PATCH] [6/6] i386: Move CONFIG_DOUBLEFAULT into arch/i386 where it belongs Andi Kleen
2006-04-18 19:05 ` Adrian Bunk
2006-04-18 20:12   ` [discuss] " Andi Kleen
2006-04-19  2:08     ` Randy.Dunlap
2006-04-20 11:49       ` Adrian Bunk [this message]
2006-04-20 13:26         ` Andi Kleen
2006-04-20 13:47           ` Adrian Bunk

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=20060420114946.GM25047@stusta.de \
    --to=bunk@stusta.de \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=torvalds@osdl.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