From: WANG Cong <xiyou.wangcong@gmail.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de,
WANG Cong <xiyou.wangcong@gmail.com>,
Adrian Bunk <bunk@kernel.org>
Subject: Re: Fwd: [-mm Patch] drivers/net/wireless/b43legacy/main.c: initialize the correct return value
Date: Mon, 15 Oct 2007 21:39:06 +0800 [thread overview]
Message-ID: <20071015133906.GR2444@hacking> (raw)
In-Reply-To: <200710151454.46047.mb@bu3sch.de>
On Mon, Oct 15, 2007 at 02:54:45PM +0200, Michael Buesch wrote:
>From: Adrian Bunk <bunk@kernel.org>
Adrian suggested to change this tag. So maybe the following is right.
Reported-by: Adrian Bunk <bunk@kernel.org>
<snip>
Thanks!
--
May the Source Be With You.
next prev parent reply other threads:[~2007-10-15 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 12:54 Fwd: [-mm Patch] drivers/net/wireless/b43legacy/main.c: initialize the correct return value Michael Buesch
2007-10-15 13:39 ` WANG Cong [this message]
2007-10-16 13:39 ` Larry Finger
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=20071015133906.GR2444@hacking \
--to=xiyou.wangcong@gmail.com \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=bunk@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
/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).