From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: mfuzzey@gmail.com
Cc: linux-serial@vger.kernel.org, tsbogend@alpha.franken.de,
linux-kernel@vger.kernel.org
Subject: Re: Serial: sc26xx device name
Date: Sat, 21 Nov 2009 23:24:40 +0000 [thread overview]
Message-ID: <20091121232440.68e9f68f@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <4B07F7E4.1070207@gmail.com>
On Sat, 21 Nov 2009 15:23:32 +0100
Martin Fuzzey <mfuzzey@gmail.com> wrote:
> Alan Cox wrote:
> >> 2) How are device name conflicts handled?
> >>
> >
> > Badly - they should never occur but if someone didn't properly reserve
> > the namespace they can and then whoever forgot to reserve the namespace
> > loses.
> >
> Currently this can't happen because the sc26xx driver uses ttySC205
> in contradiction to ttySC0 shown in devices.txt
I'd suggest that someone fixes it when it happens in that case. I doubt
it ever will.
prev parent reply other threads:[~2009-11-21 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 13:51 Serial: sc26xx device name Martin Fuzzey
2009-11-21 14:09 ` Alan Cox
2009-11-21 14:23 ` Martin Fuzzey
2009-11-21 23:24 ` Alan Cox [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=20091121232440.68e9f68f@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mfuzzey@gmail.com \
--cc=tsbogend@alpha.franken.de \
/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