From: Kalle Valo <kvalo@codeaurora.org>
To: Amitkumar Karwar <amitkarwar@gmail.com>
Cc: linux-wireless@vger.kernel.org,
Amitkumar Karwar <amit.karwar@redpinesignals.com>
Subject: Re: [PATCH 00/17] rsi: station enhancements
Date: Tue, 27 Jun 2017 17:26:44 +0300 [thread overview]
Message-ID: <87h8z1bj6j.fsf@codeaurora.org> (raw)
In-Reply-To: <1498226856-6305-1-git-send-email-amit.karwar@redpinesignals.com> (Amitkumar Karwar's message of "Fri, 23 Jun 2017 19:37:19 +0530")
Amitkumar Karwar <amitkarwar@gmail.com> writes:
> We have internal management frames(commands) sent to firmware for
> various configurations. This patch defines some common structures
> which can be shared by those frames. Key handling and regulatory
> enhancements are also includesd. With this patch series included,
> station can connect to security enabled AP and send/receive data.
Are you saying that before rsi driver was not able to connect a security
enabled AP? Just trying to understand the status.
> Prameela Rani Garnepudi (17):
> rsi: add common structures needed for command packets
> rsi: immediate wakeup bit and priority for TX command packets
> rsi: Update in tx command frame radio capabilities
> rsi: remove unnecessary check for 802.11 management packet
> rsi: Update peer notify command frame
> rsi: Update aggregation parameters command frame
> rsi: Update baseband RF programming frame
> rsi: update set_channel command frame
> rsi: update vap capabilities command frame
> rsi: update set_key command frame
> rsi: set_key enhancements
> rsi: update autorate request command frame
> rsi: block/unblock data queues as per connection status
> rsi: update tx command frame block/unblock data
> rsi: Remove internal header from Tx status skb
> rsi: Send rx filter frame to device when interface is down
> rsi: regulatory enhancements
Also in the future please try to keep the size of patchsets in
reasonable sizes. Something like max 10-12 patches per set is usually
ok, dependinging on the size of patches of course. But anything more
than that and the review becomes too annoying.
--
Kalle Valo
next prev parent reply other threads:[~2017-06-27 14:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 14:07 [PATCH 00/17] rsi: station enhancements Amitkumar Karwar
2017-06-23 14:07 ` [PATCH 01/17] rsi: add common structures needed for command packets Amitkumar Karwar
2017-06-23 14:07 ` [PATCH 02/17] rsi: immediate wakeup bit and priority for TX " Amitkumar Karwar
2017-06-23 14:07 ` [PATCH 03/17] rsi: Update in tx command frame radio capabilities Amitkumar Karwar
2017-06-23 14:07 ` [PATCH 04/17] rsi: remove unnecessary check for 802.11 management packet Amitkumar Karwar
2017-06-23 14:07 ` [PATCH 05/17] rsi: Update peer notify command frame Amitkumar Karwar
2017-06-23 14:07 ` [PATCH 06/17] rsi: Update aggregation parameters " Amitkumar Karwar
2017-06-23 14:07 ` [PATCH 07/17] rsi: Update baseband RF programming frame Amitkumar Karwar
2017-06-23 14:07 ` [PATCH 08/17] rsi: update set_channel command frame Amitkumar Karwar
2017-06-23 14:07 ` [PATCH 09/17] rsi: update vap capabilities " Amitkumar Karwar
2017-06-23 14:07 ` [PATCH 10/17] rsi: update set_key " Amitkumar Karwar
2017-06-23 14:07 ` [PATCH 11/17] rsi: set_key enhancements Amitkumar Karwar
2017-06-23 14:07 ` [PATCH 12/17] rsi: update autorate request command frame Amitkumar Karwar
2017-06-23 14:07 ` [PATCH 13/17] rsi: block/unblock data queues as per connection status Amitkumar Karwar
2017-06-23 14:07 ` [PATCH 14/17] rsi: update tx command frame block/unblock data Amitkumar Karwar
2017-06-23 14:07 ` [PATCH 15/17] rsi: Remove internal header from Tx status skb Amitkumar Karwar
2017-06-23 14:07 ` [PATCH 16/17] rsi: Send rx filter frame to device when interface is down Amitkumar Karwar
2017-06-23 14:07 ` [PATCH 17/17] rsi: regulatory enhancements Amitkumar Karwar
2017-06-27 14:26 ` Kalle Valo [this message]
2017-06-28 6:31 ` [PATCH 00/17] rsi: station enhancements Amitkumar Karwar
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=87h8z1bj6j.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=amit.karwar@redpinesignals.com \
--cc=amitkarwar@gmail.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;
as well as URLs for NNTP newsgroup(s).