From: Johannes Berg <johannes@sipsolutions.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 1/3] mac80211: put rx handlers into seperate functions
Date: Mon, 02 Aug 2010 15:22:25 +0200 [thread overview]
Message-ID: <1280755345.3923.13.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <201008021515.06013.chunkeey@googlemail.com>
On Mon, 2010-08-02 at 15:15 +0200, Christian Lamparter wrote:
> Note: In order to keep diff from removing and re-adding code,
> I used forward declarations. So it should be easier to verify
> that I didn't change anything related to the reordering logic.
FWIW, I'd prefer you didn't do that but moved the code instead.
johannes
prev parent reply other threads:[~2010-08-02 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 13:15 [PATCH 1/3] mac80211: put rx handlers into seperate functions Christian Lamparter
2010-08-02 13:22 ` 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=1280755345.3923.13.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).