Re: sdio: About pointers in sdio_device_id::driver_data

["Uwe Kleine-König" <u.kleine-koenig@baylibre.com>]

[-- Attachment #1: Type: text/plain, Size: 1739 bytes --]

Hello,

some feedback for this mail:

On Fri, Apr 17, 2026 at 07:11:42AM -0700, bluez.test.bot@gmail.com wrote:
> This is an automated email and please do not reply to this email.

I hope it's ok to ignore this request here :-)

> While preparing the CI tests, the patches you submitted couldn't be applied to the current HEAD of the repository.

It would be great to point out the URL and commit hash of this current
HEAD to simplify acting on that and also be able to understand the
details of the mail in a few weeks when the repository probably got a
few more commits.

Having said that, the patch series fits on top of
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git's
HEAD currently at bc39a094730c ("Bluetooth: hci_sync: fix stack buffer
overflow in hci_le_big_create_sync"). But I guess "the repository" is
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git
that indeed contains a conflicting commit.

Assuming that the series being applicable to the bluetooth HEAD isn't
the only test done here, a great way to make the bot reply more useful
would be to honor

	base-commit: 028ef9c96e96197026887c0f092424679298aae8

from the cover letter and then provide more test results (after pointing
out that the wrong base was chosen).

> ----- Output -----
> 
> error: patch failed: drivers/bluetooth/btmtksdio.c:64
> error: drivers/bluetooth/btmtksdio.c: patch does not apply
> hint: Use 'git am --show-current-patch' to see the failed patch
> 
> Please resolve the issue and submit the patches again.

Given that the bluetooth parts are not ready for application now without
the first patch in the series, I won't do that now.

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]