From: Andrew Morton <akpm@linux-foundation.org>
To: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
Cc: Adrian Bunk <bunk@stusta.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
takada <takada@mbf.nifty.com>,
Jordan Crouse <jordan.crouse@amd.com>,
linux-kernel@vger.kernel.org
Subject: Re: Please revert "fix typo in geode_configre()@cyrix.c"
Date: Fri, 2 Feb 2007 13:18:54 -0800 [thread overview]
Message-ID: <20070202131854.d5ea9de7.akpm@osdl.org> (raw)
In-Reply-To: <20070202151236.GN7582@csclub.uwaterloo.ca>
On Fri, 2 Feb 2007 10:12:36 -0500
lsorense@csclub.uwaterloo.ca (Lennart Sorensen) wrote:
> On Fri, Feb 02, 2007 at 12:05:43AM -0800, Andrew Morton wrote:
> > On Fri, 2 Feb 2007 07:29:41 +0100 Adrian Bunk <bunk@stusta.de> wrote:
> >
> > > Linus, please revert commit e4f0ae0ea63caceff37a13f281a72652b7ea71ba
> > >
> >
> > Yup.
> >
> > That discussion seems to have died. The 2.6.19 code looks rather silly, but
> > presumably it passed someone's testing at some stage.
>
> The discussion ended because the last patch seemed to be correct to
> everyone involved in the discussion. At least that is my understanding.
> Of course I am just one of the users affected by the patch.
The discussion ended with me asking for someone to send a patch. That
hasn't happened yet. I don't want to have to troll through 20-30 messages
and try to work out what patch we ended up with - that's the way in which
mistakes occur.
Linus has now reverted e4f0ae0ea63caceff37a13f281a72652b7ea71ba. Now,
please, could someone send a patch against either current -git or against
2.6.19? One which includes a descriptin of what it does, and why.
Thanks.
next prev parent reply other threads:[~2007-02-02 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 6:29 Adrian Bunk
2007-02-02 8:05 ` Andrew Morton
2007-02-02 15:12 ` Lennart Sorensen
2007-02-02 21:18 ` Andrew Morton [this message]
2007-02-03 5:52 ` TAKADA Yoshihito
2007-02-02 8:40 ` Juergen Beisert
2007-02-02 15:11 ` Lennart Sorensen
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=20070202131854.d5ea9de7.akpm@osdl.org \
--to=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=jordan.crouse@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=takada@mbf.nifty.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®