Received-SPF: pass (google.com: domain of linux-kernel+bounces-107485-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Date: Tue, 19 Mar 2024 12:51:34 +0100
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
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
Message-ID: <2024031905-showpiece-coral-c76c@gregkh>
References: <20240318080126.2813476-1-sakari.ailus@linux.intel.com>
 <2024031915-manhole-winnings-43d4@gregkh>
 <ZfltTgGANYs9uix5@kekkonen.localdomain>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ZfltTgGANYs9uix5@kekkonen.localdomain>

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.

thanks,

greg k-h