From: Tejun Heo <teheo@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg KH <greg@kroah.com>, Al Viro <viro@ftp.linux.org.uk>,
Takashi Iwai <tiwai@suse.de>,
Linux Kernel <linux-kernel@vger.kernel.org>,
cguthrie@mandriva.org
Subject: Re: [PATCH 2/2] sound: make OSS device number claiming optional
Date: Thu, 06 Aug 2009 01:52:26 +0900 [thread overview]
Message-ID: <4A79B8CA.8050504@suse.de> (raw)
In-Reply-To: <20090805173346.130d80bb@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>> I don't see how I would be able to achieve the latter with one liner.
>> Can you please elaborate a little bit?
>
> It depends how much of a hurry you are in, but for the mainstream we can
> do this
>
> 1. Make soundcore also issue the request_module() as if the char
> minor was unclaimed. Mark the old one as obsolete
>
> 2. Wait a year while people adjust their scripts to trigger on the
> char event instead (and fix the ordering bits for ALSA if the soundcore
> docs are still valid on that)
>
> 3. Apply a patch which makes ALSA use char dev allocation directly
> for its OSS devices and dumps out soundcore, remove soundcore and switch
> any other code using it.
It's quite difficult to think that those now mostly unused module
alises are worth full year of waiting and careful coordination. I
think we're chasing a non-issue here. If it really matters, I'll try
to teach chrdev about alternative module alises.
If you think the above is a good solution, how about the following?
1. Merge the weird switch thing and the extra standard chrdev module
alias patch
2. Add to feature-removal that snd-slot/service-* are going away in a
year along with the weird switches. This allows people who wish to
try or switch in the meantime to do so.
3. After a year, drop module loading related code from sound_core
along with the weird config option and kernel parameter.
In the end, the only choice we have to make is whether to keep
snd-slot/service-* aliases. If we're gonna (I don't see why tho), the
cleanest way would be to teach chrdev about aliases. If not, the best
way is to add a switch so that it can be phased out gradually.
Thanks.
--
tejun
next prev parent reply other threads:[~2009-08-05 16:50 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 6:35 [PATCH 1/2] chrdev: implement __[un]register_chrdev() Tejun Heo
2009-08-05 6:40 ` [PATCH 2/2] sound: make OSS device number claiming optional Tejun Heo
2009-08-05 9:15 ` Alan Cox
2009-08-05 9:24 ` Colin Guthrie
2009-08-05 9:59 ` Alan Cox
2009-08-05 10:14 ` Takashi Iwai
2009-08-05 10:26 ` Alan Cox
2009-08-05 10:45 ` Takashi Iwai
2009-08-05 11:15 ` Alan Cox
2009-08-05 11:34 ` Tejun Heo
2009-08-05 12:35 ` Tejun Heo
2009-08-05 13:11 ` Alan Cox
2009-08-05 14:16 ` Tejun Heo
2009-08-05 9:32 ` Tejun Heo
2009-08-05 10:00 ` Alan Cox
2009-08-05 11:27 ` Tejun Heo
2009-08-05 12:48 ` Alan Cox
2009-08-05 14:13 ` Tejun Heo
2009-08-05 14:29 ` Alan Cox
2009-08-05 16:02 ` Tejun Heo
2009-08-05 16:33 ` Alan Cox
2009-08-05 16:38 ` Alan Cox
2009-08-05 16:52 ` Tejun Heo [this message]
2009-08-05 17:01 ` Alan Cox
2009-08-06 5:55 ` Tejun Heo
2009-08-05 7:04 ` [PATCH 1/2] chrdev: implement __[un]register_chrdev() Takashi Iwai
2009-08-05 7:11 ` Tejun Heo
2009-08-05 7:20 ` Takashi Iwai
2009-08-05 7:30 ` Tejun Heo
2009-08-05 9:01 ` [PATCH 1/2 UPDATED] " Tejun Heo
2009-08-05 16:16 ` [PATCH 1/2] " Greg KH
2009-08-05 16:30 ` Tejun Heo
2009-08-05 16:49 ` Greg KH
2009-08-05 17:01 ` Tejun Heo
2009-08-05 17:15 ` Greg KH
2009-08-06 5:52 ` Tejun Heo
2009-08-06 8:13 ` Tejun Heo
2009-08-06 19:58 ` Greg KH
2009-08-07 2:34 ` Tejun Heo
2009-08-07 4:05 ` Greg KH
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=4A79B8CA.8050504@suse.de \
--to=teheo@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cguthrie@mandriva.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=viro@ftp.linux.org.uk \
/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