From: Claire Chang <tientzu@chromium.org>
To: Balakrishna Godavarthi <bgodavar@codeaurora.org>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
Matthias Kaehlcke <mka@chromium.org>,
linux-bluetooth@vger.kernel.org, hemantg@codeaurora.org,
linux-arm-msm@vger.kernel.org, Rocky Liao <rjliao@codeaurora.org>,
c_hbandi@codeaurora.org
Subject: Re: [PATCH v2] Bluetooth: btqca: Reset download type to default
Date: Thu, 8 Aug 2019 17:11:13 +0800 [thread overview]
Message-ID: <CALiNf2_ba1XEsHX1bgMrUtJih5DFTwFmWU+6mizN9DnDZx0FUw@mail.gmail.com> (raw)
In-Reply-To: <20190808085608.18010-1-bgodavar@codeaurora.org>
Tested-by: Claire Chang <tientzu@chromium.org>
Reviewed-by: Claire Chang <tientzu@chromium.org>
Thanks!
On Thu, Aug 8, 2019 at 4:56 PM Balakrishna Godavarthi
<bgodavar@codeaurora.org> wrote:
>
> This patch will reset the download flag to default value
> before retrieving the download mode type.
>
> Fixes: 32646db8cc28 ("Bluetooth: btqca: inject command complete event during fw download")
> Signed-off-by: Balakrishna Godavarthi <bgodavar@codeaurora.org>
> ---
> v2:
> * add fix tag.
>
> ---
> drivers/bluetooth/btqca.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/bluetooth/btqca.c b/drivers/bluetooth/btqca.c
> index 2221935fac7e..9fb247c10855 100644
> --- a/drivers/bluetooth/btqca.c
> +++ b/drivers/bluetooth/btqca.c
> @@ -140,6 +140,7 @@ static void qca_tlv_check_data(struct rome_config *config,
> BT_DBG("Length\t\t : %d bytes", length);
>
> config->dnld_mode = ROME_SKIP_EVT_NONE;
> + config->dnld_type = ROME_SKIP_EVT_NONE;
>
> switch (config->type) {
> case TLV_TYPE_PATCH:
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
>
next prev parent reply other threads:[~2019-08-08 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 8:56 [PATCH v2] Bluetooth: btqca: Reset download type to default Balakrishna Godavarthi
2019-08-08 9:11 ` Claire Chang [this message]
2019-08-12 17:08 ` Marcel Holtmann
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=CALiNf2_ba1XEsHX1bgMrUtJih5DFTwFmWU+6mizN9DnDZx0FUw@mail.gmail.com \
--to=tientzu@chromium.org \
--cc=bgodavar@codeaurora.org \
--cc=c_hbandi@codeaurora.org \
--cc=hemantg@codeaurora.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mka@chromium.org \
--cc=rjliao@codeaurora.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).