All of lore.kernel.org
 help / color / mirror / Atom feed
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 changes for v5.9 merge window
Date: Tue, 21 Jul 2020 14:09:33 +0200	[thread overview]
Message-ID: <20200721120933.GA1826843@kroah.com> (raw)
In-Reply-To: <20200721114252.GD5180@lahna.fi.intel.com>

On Tue, Jul 21, 2020 at 02:42:52PM +0300, Mika Westerberg wrote:
> Hi Greg,
> 
> The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
> 
>   Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git tags/thunderbolt-for-v5.9

Pulled and pushed out, thanks.

> for you to fetch changes up to ef7e12078ab832c72315adcfa05e7a9498a5e109:
> 
>   thunderbolt: Fix old style declaration warning (2020-07-02 14:50:11 +0300)
> 
> ----------------------------------------------------------------
> thunderbolt: Changes for v5.9 merge window
> 
> This includes following Thunderbolt/USB4 changes for v5.9 merge window:
> 
>   * Improvements around NHI (Native Host Interface) HopID allocation
> 
>   * Improvements to tunneling and USB3 bandwidth management support
> 
>   * Add KUnit tests for path walking and tunneling
> 
>   * Initial support for USB4 retimer firmware upgrade
> 
>   * Implement Thunderbolt device firmware upgrade mechanism that runs
>     the NVM image authentication when the device is disconnected.
> 
>   * A couple of small non-critical fixes
> 
> ----------------------------------------------------------------
> 
> Please notice when merged with kunit-next tree there will be a build
> error because the one member (allocation) of struct kunit_resource was
> renamed with linux-next commit d4cdd146d0db ("kunit: generalize
> kunit_resource API beyond allocated resources"). Linux-next carries a
> fix that is at the end of this email to solve the issue (from Stephen
> Rothwell).
> 
> Let me know if you prefer that I merge kunit-next branch to my -next
> branch and resolve it there first.

Nah, that branch can worry about things when it gets to Linus :)

thanks,

greg k-h

      reply	other threads:[~2020-07-21 12:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 11:42 [GIT PULL] Thunderbolt/USB4 changes for v5.9 merge window Mika Westerberg
2020-07-21 12:09 ` Greg Kroah-Hartman [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=20200721120933.GA1826843@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 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.