From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Jouni Malinen <j@w1.fi>,
Jouni Malinen <jouni.malinen@atheros.com>,
wireless <linux-wireless@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
John Linville <linville@tuxdriver.com>,
Jean Tourrilhes <jt@hpl.hp.com>
Subject: Re: Regression in 2.6.27-git from commit 43ac2ca3840f64
Date: Wed, 22 Oct 2008 19:06:29 +0200 [thread overview]
Message-ID: <1224695189.30459.6.camel@johannes.berg> (raw)
In-Reply-To: <48FF5933.3080501@lwfinger.net> (sfid-20081022_184755_577051_32659A3C)
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
On Wed, 2008-10-22 at 09:47 -0700, Larry Finger wrote:
> When a utility starts spitting messages that it doesn't understand what the
> kernel is providing _AND_ the commit message does not mention that this will
> happen, can someone be blamed for thinking it is a bug?
Heh, no, not really. It was fairly obvious us, but I guess we were just
routine-blinded.
> Clearly this is not a regression. Are there plans to update the wireless utilities?
I suspect it could just be made to ignore them. Or skip a select few,
but obviously it will never be able to parse all of them...
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-10-22 17:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 16:01 Larry Finger
2008-10-21 21:30 ` Johannes Berg
2008-10-22 2:34 ` Larry Finger
2008-10-22 7:23 ` Johannes Berg
2008-10-21 21:37 ` John W. Linville
2008-10-22 2:45 ` Larry Finger
2008-10-22 7:28 ` Jouni Malinen
2008-10-22 16:47 ` Larry Finger
2008-10-22 17:04 ` Jouni Malinen
2008-10-22 17:06 ` Johannes Berg [this message]
2008-10-22 17:37 ` Jean Tourrilhes
2008-10-22 17:46 ` Johannes Berg
2008-10-22 18:00 ` Jean Tourrilhes
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=1224695189.30459.6.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=j@w1.fi \
--cc=jouni.malinen@atheros.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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
all inboxes | Powered by JetHome®