All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v1] Bluetooth: hci_event: Fix sending MGMT_EV_DEVICE_FOUND for invalid address
Date: Wed, 02 Apr 2025 21:10:37 +0000	[thread overview]
Message-ID: <174362823758.1678044.14052016013453471857.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250401171013.3785788-1-luiz.dentz@gmail.com>

Hello:

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

On Tue,  1 Apr 2025 13:10:13 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> This fixes sending MGMT_EV_DEVICE_FOUND for invalid address
> (00:00:00:00:00:00) which is a regression introduced by
> a2ec905d1e16 ("Bluetooth: fix kernel oops in store_pending_adv_report")
> since in the attempt to skip storing data for extended advertisement it
> actually made the code to skip the entire if statement supposed to send
> MGMT_EV_DEVICE_FOUND without attempting to use the last_addr_adv which
> is garanteed to be invalid for extended advertisement since we never
> store anything on it.
> 
> [...]

Here is the summary with links:
  - [v1] Bluetooth: hci_event: Fix sending MGMT_EV_DEVICE_FOUND for invalid address
    https://git.kernel.org/bluetooth/bluetooth-next/c/32b70317f41c

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



      parent reply	other threads:[~2025-04-02 21:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01 17:10 [PATCH v1] Bluetooth: hci_event: Fix sending MGMT_EV_DEVICE_FOUND for invalid address Luiz Augusto von Dentz
2025-04-01 17:32 ` [v1] " bluez.test.bot
2025-04-02 21:10 ` 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=174362823758.1678044.14052016013453471857.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.