From: Greg KH <gregkh@linuxfoundation.org>
To: Christian Eggers <ceggers@arri.de>
Cc: stable@vger.kernel.org, linux-bluetooth@vger.kernel.org,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Subject: Re: [PATCH 6.6.y] Bluetooth: HCI: Set extended advertising data synchronously
Date: Mon, 7 Jul 2025 10:11:32 +0200 [thread overview]
Message-ID: <2025070719-kerchief-framing-0e14@gregkh> (raw)
In-Reply-To: <20250707080204.21335-2-ceggers@arri.de>
On Mon, Jul 07, 2025 at 10:02:05AM +0200, Christian Eggers wrote:
> Currently, for controllers with extended advertising, the advertising
> data is set in the asynchronous response handler for extended
> adverstising params. As most advertising settings are performed in a
> synchronous context, the (asynchronous) setting of the advertising data
> is done too late (after enabling the advertising).
>
> Move setting of adverstising data from asynchronous response handler
> into synchronous context to fix ordering of HCI commands.
>
> Signed-off-by: Christian Eggers <ceggers@arri.de>
> Fixes: a0fb3726ba55 ("Bluetooth: Use Set ext adv/scan rsp data if controller supports")
> Cc: stable@vger.kernel.org
> v2: https://lore.kernel.org/linux-bluetooth/20250626115209.17839-1-ceggers@arri.de/
> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> ---
> net/bluetooth/hci_event.c | 36 -------
> net/bluetooth/hci_sync.c | 213 ++++++++++++++++++++++++--------------
> 2 files changed, 133 insertions(+), 116 deletions(-)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2025-07-07 8:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025070625-wafer-speed-20c1@gregkh>
2025-07-07 8:02 ` [PATCH 6.6.y] Bluetooth: HCI: Set extended advertising data synchronously Christian Eggers
2025-07-07 8:11 ` Greg KH [this message]
2025-07-07 8:24 ` [6.6.y] " bluez.test.bot
2025-07-07 8:13 ` [PATCH 6.6.y] " Christian Eggers
2025-07-08 15:36 ` Greg KH
2025-07-08 15:56 ` Luiz Augusto von Dentz
2025-07-08 21:14 ` Christian Eggers
2025-07-09 6:19 ` Greg KH
2025-07-09 9:05 ` [PATCH 6.6.y v2] " Christian Eggers
2025-07-09 9:20 ` [6.6.y,v2] " bluez.test.bot
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=2025070719-kerchief-framing-0e14@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ceggers@arri.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=stable@vger.kernel.org \
/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