From: Johannes Berg <johannes@sipsolutions.net>
To: Felix Fietkau <nbd@openwrt.org>,
Janusz Dziedzic <janusz.dziedzic@tieto.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] mac80211: add NEED_ALIGNED4_SKBS hw flag
Date: Tue, 23 Feb 2016 17:15:01 +0100 [thread overview]
Message-ID: <1456244101.9910.21.camel@sipsolutions.net> (raw)
In-Reply-To: <56CC725D.1080209@openwrt.org>
On Tue, 2016-02-23 at 15:53 +0100, Felix Fietkau wrote:
> > Perhaps we could live with this being done only for the fast-xmit
> > case?
> I don't think we should pass padded vs non-padded frames depending on
> whether fast-xmit was used. The non-fast-xmit codepath could simply
> do the memmove at the end of the tx handlers though.
I guess that's fair. Would it be sufficent though?
johannes
next prev parent reply other threads:[~2016-02-23 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 10:01 [PATCH 1/2] mac80211: add hdrlen to ieee80211_tx_data Janusz Dziedzic
2016-02-19 10:01 ` [PATCH 2/2] mac80211: add NEED_ALIGNED4_SKBS hw flag Janusz Dziedzic
2016-02-23 14:29 ` Johannes Berg
2016-02-23 14:53 ` Felix Fietkau
2016-02-23 16:15 ` Johannes Berg [this message]
2016-04-05 12:26 ` Johannes Berg
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=1456244101.9910.21.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=janusz.dziedzic@tieto.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.org \
/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).