mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Valette <eric.valette@free.fr>
To: "Von Dentz, Luiz" <luiz.von.dentz@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: your recently submitted patch to fix BT RIP error shall be applied to 6.6 stable (I have a systematic crash on reboot in 6.6.23)
Date: Wed, 27 Mar 2024 17:37:03 +0100	[thread overview]
Message-ID: <1e37c6e5-7565-4564-8caf-3290cef6d134@free.fr> (raw)
In-Reply-To: <4f0de5c3-8e33-4f2a-a39a-c7efe528fa04@free.fr>

On 27/03/2024 15:10, Eric Valette wrote:
> On 27/03/2024 15:01, Von Dentz, Luiz wrote:
>> Hi Eric,
>>
>> Then it must have been backported, which is kind of odd given that it 
>> was just merged for an -rc release that is still not consider stable, 
>> anyway the real culprit might actually be the following:
>>
>> https://patchwork.kernel.org/project/bluetooth/patch/20240327140855.896095-1-kiran.k@intel.com/
> 
> 
> Reading the patch, I'm afraid, if I apply the patch bt will then not 
> work if I reboot which is not what I want (I suspect  the firmware is 
> probably not unloaded when rebooting). Or am I making wrong assumptions?
> 
> NB: I may try to be sure...

Only get the first error and bt is still functional. Thanks.

Do not forget to queue the fix for stable.

-- eric


      reply	other threads:[~2024-03-27 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27 13:14 Eric Valette
     [not found] ` <PH0PR11MB512628ED33CB0EC120ECC08AD3342@PH0PR11MB5126.namprd11.prod.outlook.com>
2024-03-27 13:41   ` Eric Valette
2024-03-27 13:46     ` Eric Valette
     [not found]       ` <PH0PR11MB5126D61336DDE016C3607997D3342@PH0PR11MB5126.namprd11.prod.outlook.com>
2024-03-27 14:10         ` Eric Valette
2024-03-27 16:37           ` Eric Valette [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=1e37c6e5-7565-4564-8caf-3290cef6d134@free.fr \
    --to=eric.valette@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.von.dentz@intel.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®