All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Winkler, Tomas" <tomas.winkler@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Usyskin, Alexander" <alexander.usyskin@intel.com>,
	"Lubart, Vitaly" <vitaly.lubart@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [char-misc-next] mei: gsc_proxy: match component when GSC is on different bus
Date: Tue, 20 Feb 2024 19:52:13 +0000	[thread overview]
Message-ID: <PH7PR11MB7605656F961FC6D31106BD47E5502@PH7PR11MB7605.namprd11.prod.outlook.com> (raw)
In-Reply-To: <2024021927-study-schilling-9dfa@gregkh>

> 
> On Sun, Feb 11, 2024 at 03:04:08PM +0200, Tomas Winkler wrote:
> > From: Alexander Usyskin <alexander.usyskin@intel.com>
> >
> > On Arrow Lake S systems, MEI is no longer strictly connected to bus 0,
> > while graphics remain exclusively on bus 0. Adapt the component
> > matching logic to accommodate this change:
> >
> > Original behavior: Required both MEI and graphics to be on the same
> > bus 0.
> >
> > New behavior: Only enforces graphics to be on bus 0 (integrated),
> > allowing MEI to reside on any bus.
> > This ensures compatibility with Arrow Lake S and maintains
> > functionality for the legacy systems.
> >
> > Cc: <stable@vger.kernel.org>
> > Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
> > Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> 
> What commit id does this fix?  How far back in stable kernels should it go?
Should be backported together with 'mei: me: add arrow lake point S DID'
And 1dd924f6885b ("mei: gsc_proxy: add gsc proxy driver")
I will send v2

Thanks
Tomas


      reply	other threads:[~2024-02-20 19:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-11 13:04 [char-misc-next] mei: gsc_proxy: match component when GSC is on different bus Tomas Winkler
2024-02-19 10:40 ` Greg Kroah-Hartman
2024-02-20 19:52   ` Winkler, Tomas [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=PH7PR11MB7605656F961FC6D31106BD47E5502@PH7PR11MB7605.namprd11.prod.outlook.com \
    --to=tomas.winkler@intel.com \
    --cc=alexander.usyskin@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=vitaly.lubart@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.