From: Johannes Berg <johannes@sipsolutions.net>
To: Rami Rosen <ramirose@gmail.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/6] mac80211: misc cleanups.
Date: Tue, 06 Jan 2009 14:03:00 +0100 [thread overview]
Message-ID: <1231246980.3503.4.camel@johannes> (raw)
In-Reply-To: <eb3ff54b0901060050q2b5e46adt283bc3e032748dc4@mail.gmail.com> (sfid-20090106_095059_109890_98D88BD1)
[-- Attachment #1: Type: text/plain, Size: 359 bytes --]
On Tue, 2009-01-06 at 10:50 +0200, Rami Rosen wrote:
> While probing into mac80211 code, I assembelled a bunch of cleanup
> patches. This patchset provides these cleanups, each one separately
> (in case any of them is rejected because of some future use I am not
> aware of, etc.).
seems fine except 5/6, but some patches are line-wrapped
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2009-01-06 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 8:50 [PATCH 0/6] mac80211: misc cleanups Rami Rosen
2009-01-06 13:03 ` 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=1231246980.3503.4.camel@johannes \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=ramirose@gmail.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