From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Sam Hartman <hartmans@debian.org>
Cc: Zhenzhong Duan <zhenzhong.duan@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: Question about dynamic minor number of misc device
Date: Tue, 21 Jan 2020 11:31:10 -0500 [thread overview]
Message-ID: <20200121163110.GK15860@mit.edu> (raw)
In-Reply-To: <CAK8P3a2aLxAgjp2_Vb0bKw-0PMVRXKtFw=2giF0MY6hgAQpQRg@mail.gmail.com>
On Tue, Jan 21, 2020 at 08:56:37AM +0100, Arnd Bergmann wrote:
> > > I think one patch to move the ones with unique names would be fine,
> > > but then separate patches for
> > >
> > > - FLASH_MINOR move and rename to avoid conflict
> > > - change speakup to dynamic minors
> > > - support for high dynamic minor numbers if you are really motivated
> > > (probably nobody needs these)
> >
> > Are we sure that reassigning minor device number conflits isn't going
> > to break systems? Especially those on random, older, architectures
> > they might not be using udev.
>
> To clarify: the only numbers that I think should be changed to dynamic
> allocation are for drivers/staging/speakup. While this is a fairly old
> subsystem, I would expect that it being staging means we can be a
> little more progressive with the changes.
Sam,
Would you happen to know how commonly used the speakup system would be
--- in particular, on non-udev systems where changing the minor number
of the device node might break some folks? Does your hardware system
use speakup, or some other interface?
Also, who would be the best people to reach out at the
linux-speakup.org project to verify what the potential impact might be
of making this change. It looks like some of the web pages are a bit
dated, so I wasn't sure what's up to date.
Thanks!!
- Ted
next prev parent reply other threads:[~2020-01-21 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 8:33 Question about dynamic minor number of misc device Zhenzhong Duan
2020-01-20 10:03 ` Arnd Bergmann
2020-01-20 10:25 ` Zhenzhong Duan
2020-01-20 10:59 ` Arnd Bergmann
2020-01-20 22:13 ` Theodore Y. Ts'o
2020-01-21 7:56 ` Arnd Bergmann
2020-01-21 16:31 ` Theodore Y. Ts'o [this message]
2020-01-21 17:54 ` Sam Hartman
2020-01-21 15:42 ` Greg Kroah-Hartman
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=20200121163110.GK15860@mit.edu \
--to=tytso@mit.edu \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=hartmans@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhenzhong.duan@gmail.com \
/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