From: Peter Zijlstra <peterz@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Pierre Ossman <drzeus-list@drzeus.cx>,
"John W. Linville" <linville@tuxdriver.com>,
Jean Tourrilhes <jt@hpl.hp.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 22bb1be4d27... breaks hal (and NM)
Date: Thu, 24 Jul 2008 14:22:04 +0200 [thread overview]
Message-ID: <1216902124.7257.325.camel@twins> (raw)
In-Reply-To: <20080724051113.fa14f7ec.akpm@linux-foundation.org>
On Thu, 2008-07-24 at 05:11 -0700, Andrew Morton wrote:
> On Thu, 24 Jul 2008 13:57:11 +0200 Peter Zijlstra <peterz@infradead.org> wrote:
>
> > On Thu, 2008-07-24 at 13:38 +0200, Johannes Berg wrote:
> > > On Thu, 2008-07-24 at 11:58 +0200, Pierre Ossman wrote:
> > > > From commit 22bb1be4d27...:
> > > >
> > > > "The /sys/class/net/*/wireless/ direcory is, as far as I know, not used
> > > > by anyone."
> > > >
> > > > Can't have been much of an investigation as HAL uses these to determine
> > > > if a card is a wireless one. Without this option, you cannot get
> > > > wireless support in NetworkManager, stranding most laptops.
> > >
> > > Bzzzzt. You suck. Go check again. Hint: try hal's git tree.
>
> err,
>
> a) don't be rude
>
> b) what's in various git trees is unuseful for making decisions
> about production kernel features.
>
> otoh the patch seems reasonable.
> So if you've enabled CONFIG_WIRELESS_EXT_SYSFS (and it correctly has
> default y) then things should continue to work OK. And the deprecation
> date of 2010 sounds reasonable. In fact generous, for us...
>
> So where's the problem?
Your two previous points, a and b.
That help text should really have mentioned current software, not future
software. And the tone of the reply.
next prev parent reply other threads:[~2008-07-24 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 9:58 22bb1be4d27... breaks hal (and NM) Pierre Ossman
2008-07-24 11:38 ` Johannes Berg
2008-07-24 11:57 ` Peter Zijlstra
2008-07-24 12:08 ` Johannes Berg
2008-07-24 12:11 ` Andrew Morton
2008-07-24 12:22 ` Peter Zijlstra [this message]
2008-07-24 12:33 ` Alistair John Strachan
2008-07-24 12:42 ` [RFC: 2.6 patch] clarify the WIRELESS_EXT_SYSFS help text Adrian Bunk
2008-07-24 12:54 ` Peter Zijlstra
2008-07-24 20:21 ` Johannes Berg
[not found] <fa.M1pe2GT5+zpRaz/wfP7Zjo6SOMU@ifi.uio.no>
[not found] ` <fa.oiNbP36FW/6wru8zoq8SWBE4P+Y@ifi.uio.no>
[not found] ` <fa.iZfkeomZo5PN4BBKKgjtHjkkGnw@ifi.uio.no>
[not found] ` <fa.cRAFIbCK4bQBxVGv6jJ9s6e4C4M@ifi.uio.no>
2008-07-24 20:13 ` 22bb1be4d27... breaks hal (and NM) Robert Hancock
2008-07-24 21:37 ` Alessandro Suardi
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=1216902124.7257.325.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=drzeus-list@drzeus.cx \
--cc=johannes@sipsolutions.net \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.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