From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Huehn <thomas@net.t-labs.tu-berlin.de>
Cc: coelho@ti.com, brcm80211-dev-list@broadcom.com,
ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
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 2/2] mac80211: Remove control.sta from struct ieee80211_tx_info and restructure tx-path
Date: Wed, 18 Jul 2012 08:48:30 +0200 [thread overview]
Message-ID: <1342594110.5310.2.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <5005CC26.6090408@net.t-labs.tu-berlin.de>
> Virtual box did the job and I found 3 drivers that somehow did not
> complain in my OpenWRT build env... thx for not playing :)... v3 is out.
See, that's why I don't want to play the game -- I could've gone back
and forth with you for like a week over multiple compile failures :-)
> I used wireless-testing and not -next,as in -next the necessary patch
> for mwlk8 is not included but in -testing. So my general question is on
> which tree to develop, on testing or next?
Well, they don't usually diverge much. I guess I can merge in
wireless-next.git and wireless.git into mac80211-next.git if there's a
problem applying. I have meetings now, will try to apply it later.
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [ath5k-devel] [PATCH 2/2] mac80211: Remove control.sta from struct ieee80211_tx_info and restructure tx-path
Date: Wed, 18 Jul 2012 08:48:30 +0200 [thread overview]
Message-ID: <1342594110.5310.2.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <5005CC26.6090408@net.t-labs.tu-berlin.de>
> Virtual box did the job and I found 3 drivers that somehow did not
> complain in my OpenWRT build env... thx for not playing :)... v3 is out.
See, that's why I don't want to play the game -- I could've gone back
and forth with you for like a week over multiple compile failures :-)
> I used wireless-testing and not -next,as in -next the necessary patch
> for mwlk8 is not included but in -testing. So my general question is on
> which tree to develop, on testing or next?
Well, they don't usually diverge much. I guess I can merge in
wireless-next.git and wireless.git into mac80211-next.git if there's a
problem applying. I have meetings now, will try to apply it later.
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Huehn <thomas@net.t-labs.tu-berlin.de>
Cc: coelho@ti.com, brcm80211-dev-list@broadcom.com,
ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
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: Re: [ath5k-devel] [PATCH 2/2] mac80211: Remove control.sta from struct ieee80211_tx_info and restructure tx-path
Date: Wed, 18 Jul 2012 08:48:30 +0200 [thread overview]
Message-ID: <1342594110.5310.2.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <5005CC26.6090408@net.t-labs.tu-berlin.de>
> Virtual box did the job and I found 3 drivers that somehow did not
> complain in my OpenWRT build env... thx for not playing :)... v3 is out.
See, that's why I don't want to play the game -- I could've gone back
and forth with you for like a week over multiple compile failures :-)
> I used wireless-testing and not -next,as in -next the necessary patch
> for mwlk8 is not included but in -testing. So my general question is on
> which tree to develop, on testing or next?
Well, they don't usually diverge much. I guess I can merge in
wireless-next.git and wireless.git into mac80211-next.git if there's a
problem applying. I have meetings now, will try to apply it later.
johannes
next prev parent reply other threads:[~2012-07-18 6:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 18:52 mac80211: Restructure ieee80211_tx_info->control to gain free space along tx-path Thomas Huehn
2012-07-13 18:52 ` [ath9k-devel] " Thomas Huehn
2012-07-13 18:52 ` [PATCH 1/2] mac80211_hwsim: fix possible race condition in usage of info->control.sta & control.vif Thomas Huehn
2012-07-13 18:52 ` [ath9k-devel] " Thomas Huehn
2012-07-13 18:52 ` [PATCH 2/2] mac80211: Remove control.sta from struct ieee80211_tx_info and restructure tx-path Thomas Huehn
2012-07-13 18:52 ` [ath9k-devel] " Thomas Huehn
2012-07-14 10:10 ` Arend van Spriel
2012-07-14 10:10 ` Arend van Spriel
2012-07-14 10:10 ` [ath9k-devel] " Arend van Spriel
2012-07-14 11:44 ` Felix Fietkau
2012-07-14 11:44 ` Felix Fietkau
2012-07-14 11:44 ` Felix Fietkau
2012-07-14 12:55 ` Arend van Spriel
2012-07-14 12:55 ` Arend van Spriel
2012-07-14 12:55 ` Arend van Spriel
2012-07-15 4:49 ` Luciano Coelho
2012-07-15 4:49 ` Luciano Coelho
2012-07-15 4:49 ` [ath9k-devel] " Luciano Coelho
2012-07-17 9:44 ` Johannes Berg
2012-07-17 9:44 ` Johannes Berg
2012-07-17 9:44 ` [ath9k-devel] " Johannes Berg
2012-07-17 12:57 ` [ath5k-devel] " Thomas Huehn
2012-07-17 12:57 ` Thomas Huehn
2012-07-17 12:57 ` [ath9k-devel] " Thomas Huehn
2012-07-17 13:03 ` Johannes Berg
2012-07-17 13:03 ` Johannes Berg
2012-07-17 13:03 ` [ath9k-devel] " Johannes Berg
2012-07-17 20:33 ` Thomas Huehn
2012-07-17 20:33 ` Thomas Huehn
2012-07-17 20:33 ` [ath9k-devel] " Thomas Huehn
2012-07-18 6:48 ` Johannes Berg [this message]
2012-07-18 6:48 ` Johannes Berg
2012-07-18 6:48 ` [ath9k-devel] " 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=1342594110.5310.2.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--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=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.