From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
Lukas Wunner <lukas@wunner.de>,
linux-usb@vger.kernel.org
Subject: Re: [GIT PULL] Thunderbolt/USB4 fix for v5.7-rc4
Date: Tue, 28 Apr 2020 19:01:31 +0200 [thread overview]
Message-ID: <20200428170131.GA1641691@kroah.com> (raw)
In-Reply-To: <20200428115815.GY487496@lahna.fi.intel.com>
On Tue, Apr 28, 2020 at 02:58:15PM +0300, Mika Westerberg wrote:
> On Tue, Apr 28, 2020 at 12:50:18PM +0200, Greg Kroah-Hartman wrote:
> > On Tue, Apr 28, 2020 at 12:09:56PM +0300, Mika Westerberg wrote:
> > > Hi Greg,
> > >
> > > The following changes since commit ae83d0b416db002fe95601e7f97f64b59514d936:
> > >
> > > Linux 5.7-rc2 (2020-04-19 14:35:30 -0700)
> > >
> > > are available in the Git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git tags/thunderbolt-fix-for-v5.7-rc4
> > >
> > > for you to fetch changes up to 9d2214b14103594efdbf33018b893b9417846d42:
> > >
> > > thunderbolt: Check return value of tb_sw_read() in usb4_switch_op() (2020-04-20 11:54:19 +0300)
> > >
> > > ----------------------------------------------------------------
> > > thunderbolt: Fix for v5.7-rc4
> > >
> > > - Fix checking return value of tb_sw_read() in usb4_switch_op().
> > >
> > > ----------------------------------------------------------------
> > > Mika Westerberg (1):
> > > thunderbolt: Check return value of tb_sw_read() in usb4_switch_op()
> >
> > Why does this commit not have a cc: stable tag on it? I can apply it by
> > hand and add it, but that will not show up as a pull request/merge, is
> > that ok?
>
> I'm not sure this qualifies as stable material to be honest. Changes
> that this triggers is really low because there are no USB4 devices
> available for public at the moment (that's the reason I did not add the
> tag).
>
> If you still think it should have stable tag, then it would be great if
> you could add it. It is fine if it goes in as a patch not a merge.
I'll add it and queue it up now, thanks.
greg k-h
next prev parent reply other threads:[~2020-04-28 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 9:09 [GIT PULL] Thunderbolt/USB4 fix for v5.7-rc4 Mika Westerberg
2020-04-28 10:50 ` Greg Kroah-Hartman
2020-04-28 11:58 ` Mika Westerberg
2020-04-28 17:01 ` Greg Kroah-Hartman [this message]
2020-04-29 9:18 ` Mika Westerberg
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=20200428170131.GA1641691@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.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;
as well as URLs for NNTP newsgroup(s).