From: "John W. Linville" <linville@tuxdriver.com>
To: Rami Rosen <ramirose@gmail.com>
Cc: linux-wireless@vger.kernel.org, reinette.chatre@intel.com
Subject: Re: [PATCH 0/2] iwlwifi: misc cleanups.
Date: Mon, 15 Dec 2008 15:39:37 -0500 [thread overview]
Message-ID: <20081215203937.GF3519@tuxdriver.com> (raw)
In-Reply-To: <eb3ff54b0812142259u576c3430x3ffd3d6c3890a9e@mail.gmail.com>
On Mon, Dec 15, 2008 at 08:59:39AM +0200, Rami Rosen wrote:
> While probing into iwlwifi code, I encountered some code which can be
> cleaned up.
> This patchset provides these cleanups.
>
> (wireless-testing).
>
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
Please post unique subjects for each patch if at all possible...
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
prev parent reply other threads:[~2008-12-15 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 6:59 [PATCH 0/2] iwlwifi: misc cleanups Rami Rosen
2008-12-15 20:39 ` 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=20081215203937.GF3519@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=ramirose@gmail.com \
--cc=reinette.chatre@intel.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;
as well as URLs for NNTP newsgroup(s).