From: Johannes Berg <johannes@sipsolutions.net>
To: alejandro.riveira@gmail.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-wireless@vger.kernel.org
Subject: Re: two different oopses with 2.6.26-rc4
Date: Wed, 28 May 2008 12:05:35 +0200 [thread overview]
Message-ID: <1211969135.21624.2.camel@johannes.berg> (raw)
In-Reply-To: <1211968234.9895.7.camel@Varda> (sfid-20080528_115058_065425_05FEB1E1)
[-- Attachment #1: Type: text/plain, Size: 352 bytes --]
> i cced wireless becouse of the first oops
Yeah. Please don't. Report one bug per email, to the appropriate forum.
wireless really doesn't want to see any debugging of weird other
problems.
Anyhow, the wireless problem here is known and a fix is on its way, so
everybody *please* drop wireless from CC if you want to reply.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2008-05-28 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 9:50 two different oopses with 2.6.26-rc4 Alejandro Riveira Fernández
2008-05-28 10:05 ` Johannes Berg [this message]
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=1211969135.21624.2.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=alejandro.riveira@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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