From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tomas Winkler <tomas.winkler@intel.com>
Cc: Alexander Usyskin <alexander.usyskin@intel.com>,
Vitaly Lubart <vitaly.lubart@intel.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [char-misc-next] mei: gsc_proxy: match component when GSC is on different bus
Date: Mon, 19 Feb 2024 11:40:01 +0100 [thread overview]
Message-ID: <2024021927-study-schilling-9dfa@gregkh> (raw)
In-Reply-To: <20240211130408.3478-1-tomas.winkler@intel.com>
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?
thanks,
greg k-h
next prev parent reply other threads:[~2024-02-19 10:40 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 [this message]
2024-02-20 19:52 ` Winkler, Tomas
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=2024021927-study-schilling-9dfa@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexander.usyskin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tomas.winkler@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox