public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	amitkumar.karwar@nxp.com, rohit.fule@nxp.com, sherry.sun@nxp.com,
	ziniu.wang_1@nxp.com, haibo.chen@nxp.com, LnxRevLi@nxp.com,
	guillaume.legoupil@nxp.com, salim.chebbo@nxp.com
Subject: Re: [PATCH v1 0/3] Enable status prints for firmware download
Date: Wed, 15 May 2024 20:00:29 +0000	[thread overview]
Message-ID: <171580322975.27792.4751752969653585130.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240515070657.85132-1-neeraj.sanjaykale@nxp.com>

Hello:

This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Wed, 15 May 2024 12:36:54 +0530 you wrote:
> This patch series enables prints for firmware download functionality to
> help any automation tests framework to verify this feature.
> 
> While testing some scenarios such as downloading corrupt FW file, if
> the driver is removed before FW download completes, or FW download
> timeout occurs, a kernel crash is observed due to Null Pointer
> Dereference, which is fixed along with a print to indicate automation
> framework that the FW Download was Aborted.
> 
> [...]

Here is the summary with links:
  - [v1,1/3] Bluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush()
    https://git.kernel.org/bluetooth/bluetooth-next/c/50f1fe988518
  - [v1,2/3] Bluetooth: btnxpuart: Enable status prints for firmware download
    https://git.kernel.org/bluetooth/bluetooth-next/c/aed74319d44d
  - [v1,3/3] Bluetooth: btnxpuart: Handle FW Download Abort scenario
    https://git.kernel.org/bluetooth/bluetooth-next/c/3b42b64036e5

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-05-15 20:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15  7:06 [PATCH v1 0/3] Enable status prints for firmware download Neeraj Sanjay Kale
2024-05-15  7:06 ` [PATCH v1 1/3] Bluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush() Neeraj Sanjay Kale
2024-05-15  7:33   ` Enable status prints for firmware download bluez.test.bot
2025-03-17 23:51   ` [PATCH v1 1/3] Bluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush() Dominique MARTINET
2025-03-20 10:20     ` Neeraj Sanjay Kale
2024-05-15  7:06 ` [PATCH v1 2/3] Bluetooth: btnxpuart: Enable status prints for firmware download Neeraj Sanjay Kale
2024-05-15  7:06 ` [PATCH v1 3/3] Bluetooth: btnxpuart: Handle FW Download Abort scenario Neeraj Sanjay Kale
2024-05-15 20:00 ` patchwork-bot+bluetooth [this message]

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=171580322975.27792.4751752969653585130.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=LnxRevLi@nxp.com \
    --cc=amitkumar.karwar@nxp.com \
    --cc=guillaume.legoupil@nxp.com \
    --cc=haibo.chen@nxp.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=neeraj.sanjaykale@nxp.com \
    --cc=rohit.fule@nxp.com \
    --cc=salim.chebbo@nxp.com \
    --cc=sherry.sun@nxp.com \
    --cc=ziniu.wang_1@nxp.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