From: Johannes Berg <johannes@sipsolutions.net>
To: Luciano Coelho <coelho@ti.com>
Cc: Thomas Huehn <thomas@net.t-labs.tu-berlin.de>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org,
ath9k-devel@venema.h4ckr.net, ath5k-devel@venema.h4ckr.net,
ilw@linux.intel.com, users@rt2x00.serialmonkey.com,
b43-dev@lists.infradead.org, brcm80211-dev-list@broadcom.com,
chunkeey@googlemail.com, buytenh@wantstofly.org, dsd@gentoo.org,
nbd@openwrt.org
Subject: [PATCH v5] mac80211: Remove control.sta from struct ieee80211_tx_info and restructure tx-path
Date: Thu, 26 Jul 2012 08:24:16 +0200 [thread overview]
Message-ID: <1343283856.4611.1.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1343244302.3750.44.camel@cumari.coelho.fi>
On Wed, 2012-07-25 at 22:25 +0300, Luciano Coelho wrote:
> > My last PATCH included some changes at a TI driver which was adapted in
> > wireless-testing in John's tree. As I touch that many drivers I would
> > like to use your tree instead, to provide a proper PATCH that builds at
> > your tree state...small de-synchronization issues just make it fail.
>
> Since Johannes has already more or less acked this patch, wouldn't it be
> easier to integrate via John's tree? I think it would make syncing with
> mac80211 and all the drivers easier.
That wouldn't have helped, I actually merged wireless-next and wireless
before applying the patch, so it just overlapped with other changes
between Thomas's testing and applying it.
johannes
next prev parent reply other threads:[~2012-07-26 6:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 20:18 [PATCH v5] mac80211: Remove control.sta from struct ieee80211_tx_info and restructure tx-path Thomas Huehn
2012-07-25 9:36 ` Johannes Berg
2012-07-25 12:50 ` Johannes Berg
2012-07-25 13:00 ` Thomas Huehn
2012-07-25 19:25 ` Luciano Coelho
2012-07-26 6:24 ` Johannes Berg [this message]
2012-07-26 9:27 ` Thomas Huehn
2012-07-26 11:57 ` Johannes Berg
2012-07-26 13:36 ` Thomas Huehn
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=1343283856.4611.1.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=ath9k-devel@venema.h4ckr.net \
--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=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=nbd@openwrt.org \
--cc=thomas@net.t-labs.tu-berlin.de \
--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