From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Marc - A. Dahlhaus" <mad@wol.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix capi devicenames
Date: Thu, 30 Sep 2010 11:56:16 +0100 [thread overview]
Message-ID: <20100930115616.633caf91@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <AANLkTik0DXVYgiDV0zy-m4kcsvX6X3j-8sGW4H_YT+x6@mail.gmail.com>
O> devices.txt is just wrong in some things, and the common userspace
> usage pattern is much closer to be a 'standard' here than this file.
> devices.txt should catch up here. The same is true for scdX vs. srX,
> scdX nodes don't exist today, and srX is not at all deprecated, unlike
> devices.txt states.
devices.txt is the spec.
> The kernel provided ISDN nodes never made sense for applications using
> ISDN. Also the devices.txt node names, I've never seen anywhere else
> than in devices.txt.
Doesn't matter - changing them will cause regressions.
If people want to rename them in userspace then fine, but changing the
default names for device nodes is not something to do lightly. You'll
break stuff for people who do follow the spec.
So NAK, and that's with the devices@lanana.org keeper of the device name
mappings hat on.
Alan
next prev parent reply other threads:[~2010-09-30 10:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 19:21 Marc - A. Dahlhaus
2010-09-30 9:30 ` Alan Cox
2010-09-30 10:08 ` Kay Sievers
2010-09-30 10:56 ` Alan Cox [this message]
2010-09-30 10:37 ` Marc - A. Dahlhaus
2010-09-30 10:50 ` Kay Sievers
2010-09-30 11:29 ` Alan Cox
2010-09-30 12:50 ` Marc - A. Dahlhaus
2010-09-30 17:35 ` Olivier Galibert
2010-09-30 19:20 ` Kay Sievers
2010-10-01 8:02 ` [PATCH] Fix capi devicenames v2 Marc - A. Dahlhaus
2010-10-01 8:36 ` [PATCH] Fix capi devicenames Marc - A. Dahlhaus
2010-10-01 9:20 ` Kay Sievers
2010-09-30 11:35 ` Alan Cox
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=20100930115616.633caf91@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mad@wol.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
all inboxes | Powered by JetHome®