From: Lee Revell <rlrevell@joe-job.com>
To: Greg KH <gregkh@suse.de>
Cc: bjdouma@xs4all.nl, Adrian Bunk <bunk@stusta.de>,
torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org,
linux-pci@atrey.karlin.mff.cuni.cz,
pcihpd-discuss@lists.sourceforge.net
Subject: Re: State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5
Date: Wed, 08 Mar 2006 19:03:49 -0500 [thread overview]
Message-ID: <1141862630.767.264.camel@mindpipe> (raw)
In-Reply-To: <20060308234004.GA31309@suse.de>
On Wed, 2006-03-08 at 15:40 -0800, Greg KH wrote:
> On Wed, Mar 08, 2006 at 06:34:54PM -0500, Lee Revell wrote:
> > On Wed, 2006-03-08 at 15:23 -0800, Greg KH wrote:
> > >
> > > > That should not go in 2.6.16 - it's not a hardware bug but a (poor IMHO)
> > > > design decision by the vendor. And, it may break working setups when an
> > > > extra sound device shows up.
> > >
> > > Ah, good thing I held off :)
> > >
> > > Any objections to it going in for 2.6.17?
> >
> > I can't think of a way to merge this and guarantee not to break
> > userspace unless it could be disabled by default.
>
> Ok, how about you and Bauke (CCed, and the author of the patch) work
> together on the problem and let me know what you decide on.
The best option might be to just take a chance on breaking things - if
userspace is so fragile that an extra sound device appearing breaks
things, it could also be broken merely by adding a new driver to the
kernel. If we have to worry about this kind of breakage the "no
incompatible changes" policy becomes "no new features".
That's my $0.02, it's between the patch author and the maintainer what
you want to do.
Lee
next prev parent reply other threads:[~2006-03-09 0:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 22:35 State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5 Greg KH
2006-03-06 22:47 ` Sam Ravnborg
2006-03-06 23:00 ` Greg KH
2006-03-08 22:26 ` Adrian Bunk
2006-03-08 22:50 ` Greg KH
2006-03-08 23:03 ` Linus Torvalds
2006-03-08 23:18 ` Greg KH
2006-03-08 23:30 ` Linus Torvalds
2006-03-09 18:40 ` Tomasz Torcz
2006-03-09 19:49 ` Linus Torvalds
2006-03-09 20:10 ` Ben Collins
2006-03-09 20:24 ` Linus Torvalds
2006-03-15 16:03 ` Ben Collins
2006-03-09 20:52 ` Lee Revell
2006-03-09 21:06 ` SMP on UP (Was Re: State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5) Ben Collins
2006-03-09 21:47 ` Lee Revell
2006-03-09 21:07 ` State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5 David S. Miller
2006-03-09 20:37 ` Arjan van de Ven
2006-03-09 20:46 ` Dave Jones
2006-03-09 21:15 ` Arjan van de Ven
2006-03-08 23:29 ` Andrew Morton
2006-03-08 23:45 ` Dave Hansen
2006-03-08 23:52 ` Andrew Morton
2006-03-09 10:24 ` Martin MOKREJŠ
2006-03-08 23:05 ` Adrian Bunk
2006-03-08 23:18 ` Lee Revell
2006-03-08 23:23 ` Greg KH
2006-03-08 23:34 ` Lee Revell
2006-03-08 23:40 ` Greg KH
2006-03-09 0:03 ` Lee Revell [this message]
2006-03-08 23:21 ` Greg KH
2006-03-09 4:01 ` Kenji Kaneshige
2006-03-09 5:34 ` Greg KH
2006-03-09 5:11 ` Lee Revell
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=1141862630.767.264.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=akpm@osdl.org \
--cc=bjdouma@xs4all.nl \
--cc=bunk@stusta.de \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=torvalds@osdl.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