From: Matt Domsch <Matt_Domsch@dell.com>
To: Martin Mares <mj@ucw.cz>
Cc: Greg KH <gregkh@suse.de>,
torvalds@osdl.org, Andrew Morton <akpm@osdl.org>,
linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: Re: State of the Linux PCI Subsystem for 2.6.18-rc6
Date: Sat, 9 Sep 2006 07:58:27 -0500 [thread overview]
Message-ID: <20060909125827.GA16084@lists.us.dell.com> (raw)
In-Reply-To: <mj+md-20060909.082546.5026.albireo@ucw.cz>
On Sat, Sep 09, 2006 at 10:39:32AM +0200, Martin Mares wrote:
> Hi Greg!
>
> > No other new PCI driver API changes are pending that I am aware of. The
> > PCI sort order change will affect some people's userspace ordering of
> > network devices, restoring it to the proper 2.4 ordering. It was never
> > intended that this be broken, and since no one has noticed this for the
> > past 3 years, it was not broken in a severe way.
>
> Changing the device order in the middle of the 2.6 cycle doesn't sound
> like a sane idea to me. Many people have changed their systems' configuration
> to adapt to the 2.6 ordering and this patch would break their setups.
> I have seen many such examples in my vicinity.
>
> I believe that not breaking existing 2.6 setups is much more important
> than keeping compatibility with 2.4 kernels, especially when the problem
> is discovered after more than 2 years after release of the first 2.6.
Respectfully, With the current 2.6 development model (i.e. the lack of
a 2.7), how are we to address this kind of thing? I'd like to see it
fixed in all new distro releases that base on 2.6.18-2.6.19, and it'll be an
individual distro decision to apply to existing releases (somewhat
unlikely). I'm open to suggestions. Udev rules like what opensuse
use would keep the existing names constant, as would the Red Hat
ifcfg-eth* method, so at least those distro users are OK. We really
need this at install time to get the naming right in the first place.
--
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2006-09-09 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-09 8:18 State of the Linux PCI Subsystem for 2.6.18-rc6 Greg KH
2006-09-09 8:39 ` Martin Mares
2006-09-09 12:58 ` Matt Domsch [this message]
2006-09-09 13:07 ` Martin Mares
2006-09-09 13:25 ` Matthew Wilcox
2006-09-17 16:23 ` 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=20060909125827.GA16084@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=mj@ucw.cz \
--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