From: "John W. Linville" <linville@tuxdriver.com>
To: Avinash Patil <patila@marvell.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Amitkumar Karwar <akarwar@marvell.com>,
Xinming Hu <huxm@marvell.com>, Marc Yang <yangyang@marvell.com>,
Cathy Luo <cluo@marvell.com>,
Maithili Hinge <maithili@marvell.com>
Subject: Re: [PATCH 00/17] mwifiex updates for 3.17
Date: Tue, 9 Sep 2014 14:25:04 -0400 [thread overview]
Message-ID: <20140909182504.GI29412@tuxdriver.com> (raw)
In-Reply-To: <CBACCFA0AEB13A41977475BCF3E896FC47819A10B6@SC-VEXCH2.marvell.com>
OK.
On Tue, Sep 09, 2014 at 10:10:01AM -0700, Avinash Patil wrote:
> Hi John,
>
> Please drop this series. I will send v2.
>
> Thanks,
> Avinash.
>
> -----Original Message-----
> From: Avinash Patil [mailto:patila@marvell.com]
> Sent: Monday, September 01, 2014 6:29 PM
> To: linville@tuxdriver.com
> Cc: linux-wireless@vger.kernel.org; Amitkumar Karwar; Xinming Hu; Marc Yang; Cathy Luo; Maithili Hinge; Avinash Patil
> Subject: [PATCH 00/17] mwifiex updates for 3.17
>
> This patch series brings in scan enhancement including scan channel gap, support for parsing FW API version from HW_SPEC command response, support for processing RX in work queue and few trivial fixes for SDIO multiport aggregation.
>
> Amitkumar Karwar (7):
> mwifiex: fix a bug in Tx multiport aggregation
> mwifiex: minor cleanup in multiport aggregation
> mwifiex: fix left_len calculation issue
> mwifiex: rename macro and variables related to API revision
> mwifiex: use firmware API revision from GET_HW_SPEC response
> mwifiex: remove redundant variable report_scan_result
> mwifiex: remove low priority scan handling
>
> Avinash Patil (9):
> mwifiex: fix probable memory corruption while processing TDLS frame
> mwifiex: avoid processing RX packets with invalid length
> mwifiex: rework internal scan for association
> mwifiex: support for event done interrupt
> mwifiex: set passive scan type for scan requests with no ssid
> mwifiex: bring in scan channel gap feature
> mwifiex: remove restriction of single channel scan when connected
> mwifiex: process TX even when scan is ongoing
> mwifiex: add rx workqueue support
>
> Xinming Hu (1):
> mwifiex: fix 5G association failure after leaving 2.4G IBSS
>
> drivers/net/wireless/mwifiex/11n_rxreorder.c | 14 ++
> drivers/net/wireless/mwifiex/cfg80211.c | 13 +-
> drivers/net/wireless/mwifiex/cmdevt.c | 28 ++--
> drivers/net/wireless/mwifiex/fw.h | 17 ++-
> drivers/net/wireless/mwifiex/init.c | 25 +++-
> drivers/net/wireless/mwifiex/main.c | 194 +++++++++++++--------------
> drivers/net/wireless/mwifiex/main.h | 49 +++++--
> drivers/net/wireless/mwifiex/pcie.c | 37 ++++-
> drivers/net/wireless/mwifiex/pcie.h | 5 +-
> drivers/net/wireless/mwifiex/scan.c | 112 ++++++++++------
> drivers/net/wireless/mwifiex/sdio.c | 28 ++--
> drivers/net/wireless/mwifiex/sta_cmd.c | 2 +-
> drivers/net/wireless/mwifiex/sta_cmdresp.c | 4 +-
> drivers/net/wireless/mwifiex/sta_ioctl.c | 13 +-
> drivers/net/wireless/mwifiex/tdls.c | 4 +-
> 15 files changed, 339 insertions(+), 206 deletions(-)
>
> --
> 1.8.1.4
>
>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2014-09-09 18:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 12:58 [PATCH 00/17] mwifiex updates for 3.17 Avinash Patil
2014-09-01 12:58 ` [PATCH 01/17] mwifiex: fix probable memory corruption while processing TDLS frame Avinash Patil
2014-09-01 12:58 ` [PATCH 02/17] mwifiex: avoid processing RX packets with invalid length Avinash Patil
2014-09-01 12:58 ` [PATCH 03/17] mwifiex: rework internal scan for association Avinash Patil
2014-09-01 12:58 ` [PATCH 04/17] mwifiex: support for event done interrupt Avinash Patil
2014-09-01 12:58 ` [PATCH 05/17] mwifiex: fix 5G association failure after leaving 2.4G IBSS Avinash Patil
2014-09-01 12:58 ` [PATCH 06/17] mwifiex: fix a bug in Tx multiport aggregation Avinash Patil
2014-09-01 12:58 ` [PATCH 07/17] mwifiex: minor cleanup in " Avinash Patil
2014-09-01 12:58 ` [PATCH 08/17] mwifiex: fix left_len calculation issue Avinash Patil
2014-09-01 12:58 ` [PATCH 09/17] mwifiex: rename macro and variables related to API revision Avinash Patil
2014-09-01 12:58 ` [PATCH 10/17] mwifiex: use firmware API revision from GET_HW_SPEC response Avinash Patil
2014-09-01 12:58 ` [PATCH 11/17] mwifiex: set passive scan type for scan requests with no ssid Avinash Patil
2014-09-01 12:59 ` [PATCH 12/17] mwifiex: bring in scan channel gap feature Avinash Patil
2014-09-01 12:59 ` [PATCH 13/17] mwifiex: remove restriction of single channel scan when connected Avinash Patil
2014-09-01 12:59 ` [PATCH 14/17] mwifiex: process TX even when scan is ongoing Avinash Patil
2014-09-01 12:59 ` [PATCH 15/17] mwifiex: remove redundant variable report_scan_result Avinash Patil
2014-09-01 12:59 ` [PATCH 16/17] mwifiex: remove low priority scan handling Avinash Patil
2014-09-01 12:59 ` [PATCH 17/17] mwifiex: add rx workqueue support Avinash Patil
2014-09-04 3:47 ` James Cameron
2014-09-05 8:08 ` Avinash Patil
2014-09-04 17:15 ` [PATCH 00/17] mwifiex updates for 3.17 John W. Linville
2014-09-04 17:22 ` Avinash Patil
2014-09-09 17:10 ` Avinash Patil
2014-09-09 18:25 ` John W. Linville [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=20140909182504.GI29412@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=akarwar@marvell.com \
--cc=cluo@marvell.com \
--cc=huxm@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=maithili@marvell.com \
--cc=patila@marvell.com \
--cc=yangyang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).