From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Yinghai Lu <Yinghai.Lu@Sun.COM>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <ak@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] serial: do not add port that is not initialized
Date: Wed, 11 Jul 2007 22:48:42 +0100 [thread overview]
Message-ID: <20070711214842.GE2301@flint.arm.linux.org.uk> (raw)
In-Reply-To: <46954150.7050707@sun.com>
On Wed, Jul 11, 2007 at 01:45:04PM -0700, Yinghai Lu wrote:
> Russell King wrote:
> >Indeed, and since distros still haven't picked up my setserial v3,
> >I see little chance of that ever being practical. Not that I've
> >really tried very hard to get them to - no real idea who to contact
> >to make that happen, and of course I've no interest in making it
> >happen anymore.
>
> so remove these extra phantom devices, the kernel distros will use your
> setserial v3.
You made a connection which wasn't there - setserial v3 doesn't allow
this either, but it is a cleaner and slightly more extensible
implementation of setserial v2.
It does, however, drop support for the things which 2.6 kernels don't
support, such as the setting of the multiport addresses and masks. So
it wouldn't be suitable for shipping as-is with (eg) 2.4 kernels.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
prev parent reply other threads:[~2007-07-11 21:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 0:03 [PATCH] serial: do not add port that is not initialized Yinghai Lu
2007-07-11 7:17 ` Russell King
2007-07-11 16:05 ` Bjorn Helgaas
2007-07-11 19:40 ` Russell King
2007-07-11 20:45 ` Yinghai Lu
2007-07-11 21:48 ` Russell King [this message]
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=20070711214842.GE2301@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=Yinghai.Lu@Sun.COM \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.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