Linux bluetooth development
 help / color / mirror / Atom feed
From: Zijun Hu <zijun.hu@oss.qualcomm.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>, Ruoyu Wang <ruoyuw560@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_qca: Clear memdump state on invalid dump size
Date: Fri, 10 Jul 2026 08:37:24 +0800	[thread overview]
Message-ID: <c56cb927-9ba4-4fff-9b2f-9dde69d9ab0b@oss.qualcomm.com> (raw)
In-Reply-To: <435c7cb7-945e-47c2-b70a-dff137f03699@molgen.mpg.de>

On 7/9/2026 3:26 PM, Paul Menzel wrote:
> 
> diff --git a/drivers/bluetooth/hci_qca.c b/drivers/bluetooth/hci_qca.c
> index b2d1ee3a3d115..1222f97800f4a 100644
> --- a/drivers/bluetooth/hci_qca.c
> +++ b/drivers/bluetooth/hci_qca.c
> @@ -1087,6 +1087,10 @@ static void qca_controller_memdump(struct work_struct *work)
>               if (!(qca_memdump->ram_dump_size)) {
>                   bt_dev_err(hu->hdev, "Rx invalid memdump size");
>                   kfree(qca_memdump);
> +                qca->qca_memdump = NULL;
> +                qca->memdump_state = QCA_MEMDUMP_COLLECTED;
> +                clear_and_wake_up_bit(QCA_MEMDUMP_COLLECTION, &qca->flags);
> +                clear_bit(QCA_IBS_DISABLED, &qca->flags);
>                   kfree_skb(skb);
>                   mutex_unlock(&qca->hci_memdump_lock);
>                   return;

Reviewed-by: Zijun Hu <zijun.hu@oss.qualcomm.com>

  reply	other threads:[~2026-07-10  0:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09  6:22 [PATCH] Bluetooth: hci_qca: Clear memdump state on invalid dump size Ruoyu Wang
2026-07-09  7:26 ` Paul Menzel
2026-07-10  0:37   ` Zijun Hu [this message]
2026-07-09  9:19 ` bluez.test.bot
2026-07-10 20:10 ` [PATCH] " patchwork-bot+bluetooth

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=c56cb927-9ba4-4fff-9b2f-9dde69d9ab0b@oss.qualcomm.com \
    --to=zijun.hu@oss.qualcomm.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=ruoyuw560@gmail.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