From: Thomas Huehn <thomas@net.t-labs.tu-berlin.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: coelho@ti.com, brcm80211-dev-list@broadcom.com,
ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
linville@tuxdriver.com, users@rt2x00.serialmonkey.com,
ilw@linux.intel.com, ath9k-devel@lists.ath9k.org,
b43-dev@lists.infradead.org, chunkeey@googlemail.com,
dsd@gentoo.org, buytenh@wantstofly.org
Subject: [ath5k-devel] [PATCH v4] mac80211: Remove control.sta from struct ieee80211_tx_info and restructure tx-path
Date: Tue, 24 Jul 2012 22:07:36 +0200 [thread overview]
Message-ID: <500F0088.6070408@net.t-labs.tu-berlin.de> (raw)
In-Reply-To: <1343141251.4415.39.camel@jlt3.sipsolutions.net>
Hi Johannes,
Johannes Berg schrieb:
> On Mon, 2012-07-23 at 21:33 +0200, Thomas Huehn wrote:
>
>> --- a/net/mac80211/ieee80211_i.h
>> +++ b/net/mac80211/ieee80211_i.h
>> @@ -196,6 +196,8 @@ struct ieee80211_tx_data {
>> struct ieee80211_channel *channel;
>>
>> unsigned int flags;
>> +
>> + struct ieee80211_tx_control control;
>
> Why is this needed/useful?
I used it just in tx.c to pass the control pointer as function
parameter, but as I like your suggestion below it is gone in v5.
>
>> info->control.vif = vif;
>> - info->control.sta = sta;
>> + control->sta = sta;
>>
>> __skb_unlink(skb, skbs);
>> - drv_tx(local, skb);
>> + drv_tx(local, control, skb);
>
> You're assigning to it right before, and I don't see you using it any
> time before, so why not just have the control struct on the stack of
> this function?
Good idea, v5 is coming.
Greetings Thomas
prev parent reply other threads:[~2012-07-24 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 19:33 [PATCH v4] mac80211: Remove control.sta from struct ieee80211_tx_info and restructure tx-path Thomas Huehn
2012-07-24 14:47 ` Johannes Berg
2012-07-24 20:07 ` Thomas Huehn [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=500F0088.6070408@net.t-labs.tu-berlin.de \
--to=thomas@net.t-labs.tu-berlin.de \
--cc=ath5k-devel@lists.ath5k.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=b43-dev@lists.infradead.org \
--cc=brcm80211-dev-list@broadcom.com \
--cc=buytenh@wantstofly.org \
--cc=chunkeey@googlemail.com \
--cc=coelho@ti.com \
--cc=dsd@gentoo.org \
--cc=ilw@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=users@rt2x00.serialmonkey.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).