From: "John W. Linville" <linville@tuxdriver.com>
To: Luciano Coelho <luciano.coelho@nokia.com>
Cc: ext Arik Nemtsov <arik@wizery.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH v2 2/2] wl1271: add support for HW TX fragmentation
Date: Thu, 11 Nov 2010 11:37:56 -0500 [thread overview]
Message-ID: <20101111163755.GC2559@tuxdriver.com> (raw)
In-Reply-To: <1289472342.1606.25.camel@powerslave>
On Thu, Nov 11, 2010 at 12:45:42PM +0200, Luciano Coelho wrote:
> On Mon, 2010-11-08 at 10:51 +0100, ext Arik Nemtsov wrote:
> > Indicate to mac80211 we support HW fragmentation.
> > Support updates of the fragmentation threshold via the
> > set_frag_threshold callback.
> >
> > Signed-off-by: Arik Nemtsov <arik@wizery.com>
> > ---
>
> Acked-by: Luciano Coelho <luciano.coelho@nokia.com>
>
> John, can you apply this directly on your tree, due to the dependency on
> mac80211? There will be a merge conflict with my next pull-request, due
> to the driver renaming, but it should be very easily solvable.
>
> The other option would be for me to wait until the mac80211 part is in
> wireless-next and only then I apply it to wl12xx.
>
> Which one would you prefer?
I'll apply them, thanks.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-11-11 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 9:51 [PATCH v2 0/2] Add support for fragmentation offload Arik Nemtsov
2010-11-08 9:51 ` [PATCH v2 1/2] mac80211: support hardware TX " Arik Nemtsov
2010-11-08 9:51 ` [PATCH v2 2/2] wl1271: add support for HW TX fragmentation Arik Nemtsov
2010-11-11 10:45 ` Luciano Coelho
2010-11-11 16:37 ` John W. Linville [this message]
2010-11-17 8:34 ` Luciano Coelho
2010-11-17 14:05 ` John W. Linville
2010-11-17 8:33 ` Luciano Coelho
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=20101111163755.GC2559@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=arik@wizery.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@nokia.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).