From: Alistair John Strachan <alistair@devzero.co.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
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 13:33:52 +0100 [thread overview]
Message-ID: <200807241333.52206.alistair@devzero.co.uk> (raw)
In-Reply-To: <20080724051113.fa14f7ec.akpm@linux-foundation.org>
On Thursday 24 July 2008 13:11:13 Andrew Morton wrote:
> : + Say Y if you have programs using it (we don't know of any).
Probably would have been less confusing if the Kconfig message actually lined
up with the note about older HALs in feature-removal-schedule.txt. Saying "we
don't know of any" seems inaccurate. This should really be something
like "old HAL versions" or perhaps even better "HAL <= X.Y.Z".
I'm sure distributors will have the common sense to stop enabling the option
in the future. In the mean time, removing the deceptive summary would
hopefully avoid such bug reports.
--
Cheers,
Alistair.
next prev parent reply other threads:[~2008-07-24 12:34 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
2008-07-24 12:33 ` Alistair John Strachan [this message]
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=200807241333.52206.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--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 \
--cc=peterz@infradead.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