Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Sergey Shtylyov <s.shtylyov@auroraos.dev>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_h5: reset hci_uart::priv in the close() method
Date: Thu, 04 Jun 2026 15:52:28 +0000	[thread overview]
Message-ID: <178058834863.2488052.14012403254228008976.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <4f997f21-786e-4745-80c1-0d6da94c0d48@auroraos.dev>

Hello:

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

On Mon, 1 Jun 2026 23:21:30 +0300 you wrote:
> Unlike the other HCI UART drivers, the 3-wire UART driver doesn't reset
> hci_uart::priv in its close() method -- this shouldn't pose a problem as
> all the methods in *struct* hci_uart_proto should only be called after the
> open() method that sets up hci_uart::priv properly. However, it seems wise
> to be more consistent and provide for the *struct* hci_uart_proto methods
> the same state that exists before the first open() method call (so that
> they rather crash than dereference a stale hci_uart::priv pointer)...
> 
> [...]

Here is the summary with links:
  - Bluetooth: hci_h5: reset hci_uart::priv in the close() method
    https://git.kernel.org/bluetooth/bluetooth-next/c/745b685608eb

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



      parent reply	other threads:[~2026-06-04 15:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01 20:21 [PATCH] Bluetooth: hci_h5: reset hci_uart::priv in the close() method Sergey Shtylyov
2026-06-01 23:46 ` bluez.test.bot
2026-06-04 15:52 ` 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=178058834863.2488052.14012403254228008976.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=s.shtylyov@auroraos.dev \
    /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