From: "John W. Linville" <linville@tuxdriver.com>
To: Ivan Kuten <ivan.kuten@promwad.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Yauhen Kharuzhy <yauhen.kharuzhy@promwad.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: fix alignment problem in scan request
Date: Mon, 10 Aug 2009 11:11:07 -0400 [thread overview]
Message-ID: <20090810151107.GC2733@tuxdriver.com> (raw)
In-Reply-To: <4A800E17.3000002@promwad.com>
On Mon, Aug 10, 2009 at 03:09:59PM +0300, Ivan Kuten wrote:
> Johannes,
>
> I can test only on compat-wireless.
Did you have to quote the whole patch (and top-post) for that?
Any reason you can't apply patches to compat-wireless?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2009-08-10 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 15:54 [PATCH] cfg80211: fix alignment problem in scan request Johannes Berg
2009-08-10 12:09 ` Ivan Kuten
2009-08-10 15:11 ` 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=20090810151107.GC2733@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ivan.kuten@promwad.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=yauhen.kharuzhy@promwad.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).