Re: [PATCH RESEND 2/2] Bluetooth: fix use-bdaddr-property quirk

[Linux regression tracking (Thorsten Leemhuis)]

On 10.07.23 14:22, Amit Pundir wrote:
> On Mon, 10 Jul 2023 at 17:14, Johan Hovold <johan@xxxxxxxxxx> wrote:
>> On Fri, Jul 07, 2023 at 07:12:35PM +0530, Amit Pundir wrote:
>>> On Fri, 7 Jul 2023 at 16:37, Johan Hovold <johan@xxxxxxxxxx> wrote:
>>>> Are there any error messages in the log when running with this patch?
>>> I don't see any relevant error message in dmesg. I'll check if I can
>>> find a command line BT debug tool which I can use on AOSP for
>>> debugging. There used to be a few hci command line tools, when I
>>> looked into it a few years ago. Not sure if they are still around and
>>> useful.
>> Yeah, I'm not sure how you set the device address with the Android
>> stack, but there must be some way as there are other bluetooth
>> controllers out there which similarly need a valid address before they
>> can be used.
> I'll look if I can reuse/simplify "btmgmt public-addr" command on
> Android or find an equivalent tool to do that.

Please correct me if I'm wrong: the avove to me sounds like you are
happy with this approach, even if this is kind of a regression; but
likely one that is rare and thus not worth making a fuzz about. In that
case I'll remove it from the regression tracking:

#regzbot resolve: minor issue, workaround found
#regzbot ignore-activity

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.