From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Huehn <thomas@net.t-labs.tu-berlin.de>
Cc: Arik Nemtsov <arik@wizery.com>,
nbd@openwrt.org, 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: [PATCH v6] mac80211: Remove control.sta from struct ieee80211_tx_info and restructure tx-path
Date: Fri, 27 Jul 2012 09:26:57 +0200 [thread overview]
Message-ID: <1343374017.4449.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <5011A250.4010500@net.t-labs.tu-berlin.de>
On Thu, 2012-07-26 at 22:02 +0200, Thomas Huehn wrote:
> > Better to just wait some time. I wrote up something to make it much
> > easier for you. Waiting for some internal review before sending it up.
> >
>
> Thx for helping out here, I ws allready checking into what kind of
> struct I can put the sta pointer. But if you have a better solution in
> mind, I wait until my v7.
When you do, please remove the last two hunks from your patch that are
spurious indentation changes in tx.c
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH v6] mac80211: Remove control.sta from struct ieee80211_tx_info and restructure tx-path
Date: Fri, 27 Jul 2012 09:26:57 +0200 [thread overview]
Message-ID: <1343374017.4449.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <5011A250.4010500@net.t-labs.tu-berlin.de>
On Thu, 2012-07-26 at 22:02 +0200, Thomas Huehn wrote:
> > Better to just wait some time. I wrote up something to make it much
> > easier for you. Waiting for some internal review before sending it up.
> >
>
> Thx for helping out here, I ws allready checking into what kind of
> struct I can put the sta pointer. But if you have a better solution in
> mind, I wait until my v7.
When you do, please remove the last two hunks from your patch that are
spurious indentation changes in tx.c
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: Arik Nemtsov <arik@wizery.com>,
nbd@openwrt.org, 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: [PATCH v6] mac80211: Remove control.sta from struct ieee80211_tx_info and restructure tx-path
Date: Fri, 27 Jul 2012 09:26:57 +0200 [thread overview]
Message-ID: <1343374017.4449.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <5011A250.4010500@net.t-labs.tu-berlin.de>
On Thu, 2012-07-26 at 22:02 +0200, Thomas Huehn wrote:
> > Better to just wait some time. I wrote up something to make it much
> > easier for you. Waiting for some internal review before sending it up.
> >
>
> Thx for helping out here, I ws allready checking into what kind of
> struct I can put the sta pointer. But if you have a better solution in
> mind, I wait until my v7.
When you do, please remove the last two hunks from your patch that are
spurious indentation changes in tx.c
johannes
next prev parent reply other threads:[~2012-07-27 7:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 16:09 [PATCH v6] mac80211: Remove control.sta from struct ieee80211_tx_info and restructure tx-path Thomas Huehn
2012-07-26 16:09 ` [ath9k-devel] " Thomas Huehn
2012-07-26 16:17 ` Johannes Berg
2012-07-26 16:17 ` Johannes Berg
2012-07-26 16:17 ` [ath9k-devel] " Johannes Berg
2012-07-26 16:19 ` Johannes Berg
2012-07-26 16:19 ` Johannes Berg
2012-07-26 16:19 ` [ath9k-devel] " Johannes Berg
2012-07-26 16:31 ` Thomas Huehn
2012-07-26 16:31 ` Thomas Huehn
2012-07-26 16:31 ` [ath9k-devel] " Thomas Huehn
2012-07-26 16:46 ` Johannes Berg
2012-07-26 16:57 ` Arik Nemtsov
2012-07-26 16:57 ` Arik Nemtsov
2012-07-26 16:57 ` [ath9k-devel] " Arik Nemtsov
2012-07-26 17:04 ` Arik Nemtsov
2012-07-26 17:04 ` Arik Nemtsov
2012-07-26 17:04 ` [ath9k-devel] " Arik Nemtsov
2012-07-26 18:41 ` Arik Nemtsov
2012-07-26 18:41 ` Arik Nemtsov
2012-07-26 18:41 ` [ath9k-devel] " Arik Nemtsov
2012-07-26 20:02 ` Thomas Huehn
2012-07-26 20:02 ` Thomas Huehn
2012-07-26 20:02 ` [ath9k-devel] " Thomas Huehn
2012-07-27 7:26 ` Johannes Berg [this message]
2012-07-27 7:26 ` Johannes Berg
2012-07-27 7:26 ` [ath9k-devel] " Johannes Berg
2012-07-27 9:35 ` Thomas Huehn
2012-07-27 9:35 ` Thomas Huehn
2012-07-27 9:35 ` [ath9k-devel] " Thomas Huehn
2012-07-27 11:52 ` Johannes Berg
2012-07-27 11:52 ` Johannes Berg
2012-07-27 11:52 ` [ath9k-devel] " Johannes Berg
2012-07-27 13:28 ` Thomas Huehn
2012-07-27 13:28 ` Thomas Huehn
2012-07-27 13:28 ` [ath9k-devel] " 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=1343374017.4449.0.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arik@wizery.com \
--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=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 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.