From: Sujith <Sujith.Manoharan@atheros.com>
To: "Guy, Wey-Yi W" <wey-yi.w.guy@intel.com>
Cc: Sujith Manoharan <Sujith.Manoharan@Atheros.com>,
Johannes Berg <johannes@sipsolutions.net>,
John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH] mac80211: fix aggregation for hardware with ampdu queues
Date: Fri, 13 Feb 2009 10:34:09 +0530 [thread overview]
Message-ID: <18836.65353.489754.511505@gargle.gargle.HOWL> (raw)
In-Reply-To: <E9954878DD1FB34FAE5187FB88C58A353F1ACF4B@orsmsx506.amr.corp.intel.com>
Guy, Wey-Yi W wrote:
> Thanks for testing. Do you agree the medium-term sulution?
>
Yep, looks okay, and doesn't seem to affect ath9k. Thanks.
Sujith
next prev parent reply other threads:[~2009-02-13 5:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 23:51 [PATCH] mac80211: fix aggregation for hardware with ampdu queues Johannes Berg
2009-02-12 4:46 ` Sujith
2009-02-12 4:55 ` Guy, Wey-Yi W
2009-02-13 5:04 ` Sujith [this message]
2009-02-13 5:11 ` Sujith
2009-02-12 9:08 ` 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=18836.65353.489754.511505@gargle.gargle.HOWL \
--to=sujith.manoharan@atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=wey-yi.w.guy@intel.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