From: Andrew Morton <akpm@linux-foundation.org>
To: Matt Mackall <mpm@selenic.com>, Adrian Bunk <bunk@stusta.de>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
yi.zhu@intel.com, jketreno@linux.intel.com,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Recent wireless breakage (ipw2200, iwconfig, NetworkManager)
Date: Sun, 4 Mar 2007 16:45:25 -0800 [thread overview]
Message-ID: <20070304164525.349f9589.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070305002550.GI23311@waste.org>
On Sun, 4 Mar 2007 18:25:50 -0600 Matt Mackall <mpm@selenic.com> wrote:
> On Mon, Mar 05, 2007 at 12:39:24AM +0100, Johannes Berg wrote:
> > [adding linux-wireless to CC]
> >
> > On Sun, 2007-03-04 at 16:08 -0600, Matt Mackall wrote:
> > > Recent kernels are having troubles with wireless for me. Two seemingly
> > > related problems:
> >
> > I don't think they are related actually.
> >
> > > a) NetworkManager seems oblivious to the existence of my IPW2200
> >
> > This is due to the recent sysfs restructuring I think. IIRC the fix is
> > to upgrade hal to a current git version.
>
> If that's the cause, the fix is to back out whatever was done to break
> userspace. Breaking userspace is not ok. Upgrading from 2.6.x to
> 2.6.x+1 should not entail replacing substantial parts of userspace,
> especially with NOT-EVEN-FRAKKING-RELEASED-YET CODE.
yep. Adrian, I think we should track this as a blocking regression, at
least until we've fully understood the implications and had the usual
arguments.
next prev parent reply other threads:[~2007-03-05 0:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070304220857.GH23311@waste.org>
2007-03-04 23:39 ` Recent wireless breakage (ipw2200, iwconfig, NetworkManager) Johannes Berg
2007-03-05 0:25 ` Matt Mackall
2007-03-05 0:45 ` Andrew Morton [this message]
2007-03-05 1:05 ` Adrian Bunk
2007-03-05 0:46 ` Ian McDonald
2007-03-05 1:17 ` Greg KH
2007-03-05 11:20 ` Johannes Berg
2007-03-05 12:59 ` Theodore Tso
2007-03-05 18:58 ` Greg KH
2007-03-05 19:55 ` Matt Mackall
2007-03-05 22:39 ` Greg KH
2007-03-06 3:07 ` Matthew Garrett
2007-03-05 23:05 ` Jeffrey Hundstad
2007-03-05 23:40 ` [2.6.21 patch] unconditionally enable SYSFS_DEPRECATED Adrian Bunk
2007-03-06 0:07 ` Greg KH
2007-03-06 0:35 ` Adrian Bunk
2007-03-06 0:41 ` Greg KH
2007-03-06 1:30 ` Matt Mackall
2007-03-06 1:56 ` Greg KH
2007-03-06 13:20 ` Johannes Berg
2007-03-06 15:55 ` Dan Williams
2007-03-06 2:48 ` Greg KH
2007-03-06 3:04 ` Matt Mackall
2007-03-06 3:39 ` Matt Mackall
2007-03-06 4:03 ` Greg KH
2007-03-06 6:10 ` Matt Mackall
2007-03-06 19:01 ` Greg KH
2007-03-06 20:05 ` Greg KH
2007-03-06 0:35 ` Recent wireless breakage (ipw2200, iwconfig, NetworkManager) Johannes Berg
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=20070304164525.349f9589.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=greg@kroah.com \
--cc=jketreno@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.org \
--cc=yi.zhu@intel.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;
as well as URLs for NNTP newsgroup(s).