From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Subject: Re: [PATCH] mac80211: minstrel_ht: don't use control.flags in TX status path
Date: Fri, 23 Aug 2013 12:01:57 +0200 [thread overview]
Message-ID: <1377252117.14021.18.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1377153566-15478-1-git-send-email-johannes@sipsolutions.net> (sfid-20130822_083934_765528_45353E2F)
On Thu, 2013-08-22 at 08:39 +0200, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> Sujith reports that my commit af61a165187bb94b1dc7628ef815c23d0eacf40b
> ("mac80211: add control port protocol TX control flag") broke ath9k
> (aggregation). The reason is that I made minstrel_ht use the flag in
> the TX status path, where it can have been overwritten by the driver.
> Since we have no more space in info->flags, revert that part of the
> change for now, until we can reshuffle the flags or so.
Applied.
johannes
prev parent reply other threads:[~2013-08-23 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 6:39 [PATCH] mac80211: minstrel_ht: don't use control.flags in TX status path Johannes Berg
2013-08-23 10:01 ` Johannes Berg [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=1377252117.14021.18.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=c_manoha@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.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