From: Kalle Valo <kvalo@codeaurora.org>
To: "Yin\, Fengwei" <fengwei.yin@linaro.org>
Cc: andy.green@linaro.org, linux-wireless@vger.kernel.org,
wcn36xx@lists.infradead.org, me@bobcopeland.com,
k.eugene.e@gmail.com, bjorn.andersson@sonymobile.com
Subject: Re: [PATCH v2 4/5] wcn3620: use new response format for wcn3620 trigger_ba
Date: Mon, 30 Nov 2015 14:46:14 +0200 [thread overview]
Message-ID: <87bnabk63t.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1447143955-10304-5-git-send-email-fengwei.yin@linaro.org> (Fengwei Yin's message of "Tue, 10 Nov 2015 03:25:54 -0500")
"Yin, Fengwei" <fengwei.yin@linaro.org> writes:
> From: Andy Green <andy.green@linaro.org>
>
> On wcn3620, firmware response to trigger_ba uses the new, larger
> "v2" format
>
> Signed-off-by: Andy Green <andy.green@linaro.org>
Please prefix the patch title with the name of driver, in this case that
would be "wcn36xx: ". This time I fixed it before I applied the patches.
--
Kalle Valo
next prev parent reply other threads:[~2015-11-30 12:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 8:25 [PATCH v2 0/5] wcn36xx: add some new firmware functionalities support Yin, Fengwei
2015-11-10 8:25 ` [PATCH v2 1/5] wcn36xx: introduce WCN36XX_HAL_AVOID_FREQ_RANGE_IND Yin, Fengwei
2015-11-30 12:44 ` [v2,1/5] " Kalle Valo
2015-11-10 8:25 ` [PATCH v2 2/5] wcn36xx: swallow two wcn3620 IND messages Yin, Fengwei
2015-11-10 8:25 ` [PATCH v2 3/5] wcn36xx: handle new hal response format Yin, Fengwei
2015-11-10 8:25 ` [PATCH v2 4/5] wcn3620: use new response format for wcn3620 trigger_ba Yin, Fengwei
2015-11-30 12:46 ` Kalle Valo [this message]
2015-11-10 8:25 ` [PATCH v2 5/5] wcn3620: use new response format for wcn3620 remove_bsskey Yin, Fengwei
2015-11-20 2:12 ` [PATCH v2 0/5] wcn36xx: add some new firmware functionalities support fengwei.yin
2015-11-22 20:03 ` Eugene Krasnikov
2015-11-23 6:54 ` yfw
2015-11-26 0:04 ` fengwei.yin
2015-11-30 11:02 ` Kalle Valo
2015-11-30 11:35 ` fengwei.yin
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=87bnabk63t.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=andy.green@linaro.org \
--cc=bjorn.andersson@sonymobile.com \
--cc=fengwei.yin@linaro.org \
--cc=k.eugene.e@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=wcn36xx@lists.infradead.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).