From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
Wentong Wu <wentong.wu@intel.com>,
Dominik Brodowski <linux@dominikbrodowski.net>
Subject: Re: [PATCH 1/1] mei: vsc: Unregister interrupt handler for system suspend
Date: Wed, 20 Mar 2024 06:45:22 +0000 [thread overview]
Message-ID: <ZfqGAth743v4Slpx@kekkonen.localdomain> (raw)
In-Reply-To: <2024031905-showpiece-coral-c76c@gregkh>
On Tue, Mar 19, 2024 at 12:51:34PM +0100, Greg Kroah-Hartman wrote:
> On Tue, Mar 19, 2024 at 10:47:42AM +0000, Sakari Ailus wrote:
> > Hi Greg,
> >
> > On Tue, Mar 19, 2024 at 08:51:43AM +0100, Greg Kroah-Hartman wrote:
> > > On Mon, Mar 18, 2024 at 10:01:26AM +0200, Sakari Ailus wrote:
> > > > Unregister the MEI VSC interrupt handler before system suspend and
> > > > re-register it at system resume time. This mirrors implementation of other
> > > > MEI devices.
> > > >
> > > > This patch fixes the bug that causes continuous stream of MEI VSC errors
> > > > after system resume.
> > > >
> > > > Fixes: 386a766c4169 ("mei: Add MEI hardware support for IVSC device")
> > > > Cc: stable@vger.kernel.org # for 6.8
> > > > Reported-by: Dominik Brodowski <linux@dominikbrodowski.net>
> > > > Signed-off-by: Wentong Wu <wentong.wu@intel.com>
> > > > Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> > > > ---
> > > > drivers/misc/mei/platform-vsc.c | 17 ++++++-
> > > > drivers/misc/mei/vsc-tp.c | 84 +++++++++++++++++++++++----------
> > > > drivers/misc/mei/vsc-tp.h | 3 ++
> > > > 3 files changed, 78 insertions(+), 26 deletions(-)
> > >
> > > What is the git commit id of this in Linus's tree?
> >
> > This one isn't in Linus's (or any other maintainer) tree yet.
>
> Then why was it sent only for 6.8? Please read:
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> for how to do this properly.
Ah, I think I mistakenly included the stable@vger e-mail address in
distribution as the other patch was meant to be sent there. I'll resend
this.
--
Sakari Ailus
prev parent reply other threads:[~2024-03-20 6:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 8:01 Sakari Ailus
2024-03-19 7:51 ` Greg Kroah-Hartman
2024-03-19 10:47 ` Sakari Ailus
2024-03-19 11:51 ` Greg Kroah-Hartman
2024-03-20 6:45 ` Sakari Ailus [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=ZfqGAth743v4Slpx@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=stable@vger.kernel.org \
--cc=wentong.wu@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®