From: Sasha Levin <sashal@kernel.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: stable <stable@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Abhishek Pandit-Subedi" <abhishekpandit@chromium.org>,
"Marcel Holtmann" <marcel@holtmann.org>,
"Max Chou" <max.chou@realtek.com>,
"Felix Dörre" <debian@felixdoerre.de>
Subject: Re: Please apply commit 24b065727ceb ("Bluetooth: Return NOTIFY_DONE for hci_suspend_notifier") to v5.8.y
Date: Mon, 7 Sep 2020 18:20:24 -0400 [thread overview]
Message-ID: <20200907222024.GP8670@sasha-vm> (raw)
In-Reply-To: <20200907200437.GA908020@eldamar.local>
On Mon, Sep 07, 2020 at 10:04:37PM +0200, Salvatore Bonaccorso wrote:
>Hi
>
>Please apply the commit 24b065727ceb ("Bluetooth: Return NOTIFY_DONE
>for hci_suspend_notifier") to the v5.8.y branch as well. As the commit
>message says it fixes actually an issue:
>
>> The original return is NOTIFY_STOP, but notifier_call_chain would stop
>> the future call for register_pm_notifier even registered on other Kernel
>> modules with the same priority which value is zero.
>
>The commit misses a Fixes tag on 9952d90ea288 ("Bluetooth: Handle
>PM_SUSPEND_PREPARE and PM_POST_SUSPEND") and so was not backported as
>well.
>
>This was affecting Felix Dörre (https://bugs.debian.org/964839#65)
>with an out of tree module, but as the commit explains the issue seem
>to be more general.
Queued up, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2020-09-07 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 20:04 Please apply commit 24b065727ceb ("Bluetooth: Return NOTIFY_DONE for hci_suspend_notifier") to v5.8.y Salvatore Bonaccorso
2020-09-07 22:20 ` Sasha Levin [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=20200907222024.GP8670@sasha-vm \
--to=sashal@kernel.org \
--cc=abhishekpandit@chromium.org \
--cc=carnil@debian.org \
--cc=debian@felixdoerre.de \
--cc=gregkh@linuxfoundation.org \
--cc=marcel@holtmann.org \
--cc=max.chou@realtek.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