All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yogesh Ashok Powar <yogeshp@marvell.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Lennert Buytenhek <buytenh@wantstofly.org>,
	Nishant Sarmukadam <nishants@marvell.com>
Subject: [PATCH 0/5] mwl8k: Support additional AMPDU streams
Date: Thu, 3 Jan 2013 13:22:18 +0530	[thread overview]
Message-ID: <20130103075214.GA20164@markyou.marvell.com> (raw)

a. Add support for additional ampdu streams 
b. Handle corresponding watchdog events to destroy ampdu streams
c. bump the fw API version

Yogesh Ashok Powar (5):
  mwl8k: Enable support to support additional ampdu streams
  mwl8k: changing mwl8k_destroy_ba prototype
  mwl8k: Handle Watchdog events for the new ampdu streams
  mwl8k: Handle watchdog event with highest prioriry
  mwl8k: bump firmware API to 3

 drivers/net/wireless/mwl8k.c | 110 ++++++++++++++++++++++++++++++++++---------
 1 file changed, 87 insertions(+), 23 deletions(-)

-- 
1.8.0.3


                 reply	other threads:[~2013-01-03  7:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20130103075214.GA20164@markyou.marvell.com \
    --to=yogeshp@marvell.com \
    --cc=buytenh@wantstofly.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=nishants@marvell.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.