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-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Thunderbolt change for v5.5 part 2
Date: Tue, 19 Nov 2019 17:00:22 +0100 [thread overview]
Message-ID: <20191119160022.GA2027670@kroah.com> (raw)
In-Reply-To: <20191119130751.GK11621@lahna.fi.intel.com>
On Tue, Nov 19, 2019 at 03:07:51PM +0200, Mika Westerberg wrote:
> Hi Greg,
>
> There is one more Thunderbolt driver improvement that I would like to
> get into v5.5 merge window. Please consider pulling.
Hey, that sounds like the problem my laptop was having! :)
Should this also go to stable for 5.4.y?
thanks,
greg k-h
next prev parent reply other threads:[~2019-11-19 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 13:07 [GIT PULL] Thunderbolt change for v5.5 part 2 Mika Westerberg
2019-11-19 16:00 ` Greg Kroah-Hartman [this message]
2019-11-19 16:20 ` Mika Westerberg
2019-11-19 16:36 ` Greg Kroah-Hartman
2019-11-20 8:30 ` 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=20191119160022.GA2027670@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-kernel@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 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.