From: Kalle Valo <kvalo@codeaurora.org>
To: Amitkumar Karwar <akarwar@marvell.com>
Cc: <linux-wireless@vger.kernel.org>, Cathy Luo <cluo@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
chunfan chen <jeffc@marvell.com>
Subject: Re: [PATCH 5/6] mwifiex: add iw vendor command support
Date: Fri, 11 Dec 2015 11:02:21 +0200 [thread overview]
Message-ID: <87eget5peq.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1449238387-27396-5-git-send-email-akarwar@marvell.com> (Amitkumar Karwar's message of "Fri, 4 Dec 2015 06:13:06 -0800")
Amitkumar Karwar <akarwar@marvell.com> writes:
> From: chunfan chen <jeffc@marvell.com>
>
> The patch allows user to
> 1. Enable turbo mode in firmware using
> following command.
> iw dev mlan0 vendor send 0x005043 0x00 0x01
>
> 2. Download configuration data to FW using
> following command
> iw dev mlan0 vendor send 0x005043 0x01 filename
>
> Signed-off-by: chunfan chen <jeffc@marvell.com>
> Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
Stuff like this gives me nightmares and I'm going to put this patch to
deferred state for now as I don't want to even think what to do. In the
mean time people can convince me should I take this or not.
--
Kalle Valo
next prev parent reply other threads:[~2015-12-11 9:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 14:13 [PATCH 1/6] mwifiex: parse adhoc start/join result Amitkumar Karwar
2015-12-04 14:13 ` [PATCH 2/6] mwifiex: handle start AP error paths correctly Amitkumar Karwar
2015-12-04 14:13 ` [PATCH 3/6] mwifiex: set regulatory info from EEPROM Amitkumar Karwar
2015-12-04 14:13 ` [PATCH 4/6] mwifiex: don't follow AP if country code received " Amitkumar Karwar
2015-12-04 14:13 ` [PATCH 5/6] mwifiex: add iw vendor command support Amitkumar Karwar
2015-12-11 9:02 ` Kalle Valo [this message]
2015-12-11 9:33 ` Amitkumar Karwar
2015-12-04 14:13 ` [PATCH 6/6] mwifiex: correction in region code to country mapping Amitkumar Karwar
2015-12-11 11:24 ` [1/6] mwifiex: parse adhoc start/join result Kalle Valo
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=87eget5peq.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=akarwar@marvell.com \
--cc=cluo@marvell.com \
--cc=jeffc@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--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 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).