From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Limonciello, Mario" <Mario.Limonciello@amd.com>
Cc: Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
"Mehta, Sanju" <Sanju.Mehta@amd.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] thunderbolt: Explicitly enable lane adapter hotplug events at startup
Date: Mon, 26 Sep 2022 20:21:25 +0300 [thread overview]
Message-ID: <YzHflTAaNaeeDEkU@black.fi.intel.com> (raw)
In-Reply-To: <MN0PR12MB61015D287945A57D82910CE4E2529@MN0PR12MB6101.namprd12.prod.outlook.com>
On Mon, Sep 26, 2022 at 02:54:22PM +0000, Limonciello, Mario wrote:
> [Public]
>
>
>
> > -----Original Message-----
> > From: Mika Westerberg <mika.westerberg@linux.intel.com>
> > Sent: Monday, September 26, 2022 09:53
> > To: Limonciello, Mario <Mario.Limonciello@amd.com>
> > Cc: Andreas Noever <andreas.noever@gmail.com>; Michael Jamet
> > <michael.jamet@intel.com>; Yehezkel Bernat <YehezkelShB@gmail.com>;
> > Mehta, Sanju <Sanju.Mehta@amd.com>; stable@vger.kernel.org; linux-
> > usb@vger.kernel.org; linux-kernel@vger.kernel.org
> > Subject: Re: [PATCH v4] thunderbolt: Explicitly enable lane adapter hotplug
> > events at startup
> >
> > Hi Mario,
> >
> > On Mon, Sep 26, 2022 at 09:33:50AM -0500, Mario Limonciello wrote:
> > > Software that has run before the USB4 CM in Linux runs may have disabled
> > > hotplug events for a given lane adapter.
> > >
> > > Other CMs such as that one distributed with Windows 11 will enable
> > hotplug
> > > events. Do the same thing in the Linux CM which fixes hotplug events on
> > > "AMD Pink Sardine".
> > >
> > > Cc: stable@vger.kernel.org
> > > Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> >
> > Looks good to me now. Since we are pretty late in the rc and this is not
> > trivial fix anymore, would it be OK for you if I apply this to my next
> > branch with stable tag? Then it gets slightly more exposure before it
> > ends up in any of the stable trees.
>
> Yeah that's fine by me, thanks!
Applied to thunderbolt.git/next, thanks!
prev parent reply other threads:[~2022-09-26 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 14:33 [PATCH v4] thunderbolt: Explicitly enable lane adapter hotplug events at startup Mario Limonciello
2022-09-26 14:53 ` Mika Westerberg
2022-09-26 14:54 ` Limonciello, Mario
2022-09-26 17:21 ` Mika Westerberg [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=YzHflTAaNaeeDEkU@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Mario.Limonciello@amd.com \
--cc=Sanju.Mehta@amd.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.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