From: "John W. Linville" <linville@tuxdriver.com>
To: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
Cc: acme@ghostprotocols.net, Jeff Garzik <jgarzik@pobox.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] drivers/net/wireless/wl3501_cs.c: remove redundant memset
Date: Wed, 8 Aug 2007 09:20:38 -0400 [thread overview]
Message-ID: <20070808132038.GA7335@tuxdriver.com> (raw)
In-Reply-To: <200708080758.22319.m.kozlowski@tuxland.pl>
On Wed, Aug 08, 2007 at 07:58:21AM +0200, Mariusz Kozlowski wrote:
> > Please send wireless patches to linux-wireless@vger.kernel.org,
> > and CC me.
>
> Ok. Did you pick the patch up?
Yes, I have it.
John
--
John W. Linville
linville@tuxdriver.com
prev parent reply other threads:[~2007-08-08 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200708070050.23158.m.kozlowski@tuxland.pl>
2007-08-07 0:11 ` [PATCH] drivers/net/wireless/wl3501_cs.c: remove redundant memset John W. Linville
2007-08-08 5:58 ` Mariusz Kozlowski
2007-08-08 13:20 ` John W. Linville [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=20070808132038.GA7335@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=acme@ghostprotocols.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m.kozlowski@tuxland.pl \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).