mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Yang Li <yang.li@amlogic.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
	luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_sync: Avoid adding default advertising on startup
Date: Mon, 28 Jul 2025 19:50:05 +0000	[thread overview]
Message-ID: <175373220501.825563.16644815912043056202.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250728-default_adv-v1-1-a1164ff502a7@amlogic.com>

Hello:

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

On Mon, 28 Jul 2025 17:08:44 +0800 you wrote:
> From: Yang Li <yang.li@amlogic.com>
> 
> list_empty(&hdev->adv_instances) is always true during startup,
> so an advertising instance is added by default.
> 
> Call trace:
>   dump_backtrace+0x94/0xec
>   show_stack+0x18/0x24
>   dump_stack_lvl+0x48/0x60
>   dump_stack+0x18/0x24
>   hci_setup_ext_adv_instance_sync+0x17c/0x328
>   hci_powered_update_adv_sync+0xb4/0x12c
>   hci_powered_update_sync+0x54/0x70
>   hci_power_on_sync+0xe4/0x278
>   hci_set_powered_sync+0x28/0x34
>   set_powered_sync+0x40/0x58
>   hci_cmd_sync_work+0x94/0x100
>   process_one_work+0x168/0x444
>   worker_thread+0x378/0x3f4
>   kthread+0x108/0x10c
>   ret_from_fork+0x10/0x20
> 
> [...]

Here is the summary with links:
  - Bluetooth: hci_sync: Avoid adding default advertising on startup
    https://git.kernel.org/bluetooth/bluetooth-next/c/b88313f2a6c3

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



      reply	other threads:[~2025-07-28 19:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28  9:08 Yang Li via B4 Relay
2025-07-28 19:50 ` 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=175373220501.825563.16644815912043056202.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --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=yang.li@amlogic.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

all inboxes | Powered by JetHome®