From: Andrew Morton <akpm@linux-foundation.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: "Jeff Garzik" <jeff@garzik.org>,
"Russell King" <rmk@arm.linux.org.uk>,
"Adam Belay" <ambx1@neo.rr.com>, "Len Brown" <lenb@kernel.org>,
"Matthew Garrett" <mjg59@srcf.ucam.org>,
"Sébastien Dugué" <sebastien.dugue@bull.net>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] x86, serial: always probe for legacy COM ports
Date: Fri, 27 Jul 2007 13:35:28 -0700 [thread overview]
Message-ID: <20070727133528.bfebb869.akpm@linux-foundation.org> (raw)
In-Reply-To: <200707271426.30962.bjorn.helgaas@hp.com>
On Fri, 27 Jul 2007 14:26:30 -0600
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> On Friday 27 July 2007 02:21:55 pm Jeff Garzik wrote:
> > Bjorn Helgaas wrote:
> > > On Friday 27 July 2007 12:05:51 pm Jeff Garzik wrote:
> > >> This is still incomplete, as repeatedly stated. Here is the email, again.
> >
> > > OK, uncle! I'll work on your helpful advice (thanks for that), but
> > > it feels too risky for this stage of 2.6.23. Maybe I can come up with
> > > something for a future release.
> >
> > The changeset in the kernel is too risky _without_ the changes I described.
>
> That's what I meant. Andrew already has a revert patch in -mm, and
> the safest path seems like putting the reversion in 2.6.23 and working
> on your advice post-2.6.23.
>
ok, thanks, I'll pull that trigger.
next prev parent reply other threads:[~2007-07-27 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 17:58 Bjorn Helgaas
2007-07-27 18:05 ` Jeff Garzik
2007-07-27 20:11 ` Bjorn Helgaas
2007-07-27 20:21 ` Jeff Garzik
2007-07-27 20:26 ` Bjorn Helgaas
2007-07-27 20:35 ` Andrew Morton [this message]
2007-07-27 20:49 ` Jeff Garzik
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=20070727133528.bfebb869.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ambx1@neo.rr.com \
--cc=bjorn.helgaas@hp.com \
--cc=jeff@garzik.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=rmk@arm.linux.org.uk \
--cc=sebastien.dugue@bull.net \
/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
Powered by JetHome