From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org
Cc: Adrian Bunk <bunk@stusta.de>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
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 15:26:21 +0200 [thread overview]
Message-ID: <200604201526.22318.ak@suse.de> (raw)
In-Reply-To: <20060420114946.GM25047@stusta.de>
On Thursday 20 April 2006 13:49, Adrian Bunk wrote:
> 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.
I just noticed a problem (bogus symbols in my x86-64 config) and fixed it. I normally
don't look at which patch it introduced for such trivial changes.
-Andi
next prev parent reply other threads:[~2006-04-20 13:26 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
2006-04-20 13:26 ` Andi Kleen [this message]
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=200604201526.22318.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--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