public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Yehezkel Bernat <yehezkelshb@gmail.com>
Cc: linux-usb@vger.kernel.org,
	Michael Jamet <michael.jamet@intel.com>,
	Lukas Wunner <lukas@wunner.de>,
	Andreas Noever <andreas.noever@gmail.com>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	kernel test robot <lkp@intel.com>, Gil Fine <gil.fine@intel.com>,
	Azhar Shaikh <azhar.shaikh@intel.com>
Subject: Re: [PATCH 0/5] thunderbolt: Support for Intel Alder Lake and improvements
Date: Fri, 11 Jun 2021 11:46:05 +0300	[thread overview]
Message-ID: <YMMizWEKEqqxPet5@lahna> (raw)
In-Reply-To: <CA+CmpXs3B-5KPzBjmyEtpY0or+0B_KHyeguFCqXuVitbqkHJug@mail.gmail.com>

On Mon, Jun 07, 2021 at 02:52:06PM +0300, Yehezkel Bernat wrote:
> On Mon, Jun 7, 2021 at 2:00 PM Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
> >
> > Hi all,
> >
> > This series adds support for Intel Alder Lake which is the successor of
> > Tiger Lake. The integrated Thunderbolt/USB4 controller is pretty close to
> > the one found in Tiger Lake too.
> >
> > In addition there are few improvements for issues reported by Dan Carpenter
> > and kernel test robot.
> >
> > The series applies on top of thunderbolt.git/next.
> >
> > Azhar Shaikh (1):
> >   thunderbolt: Add support for Intel Alder Lake
> >
> > Gil Fine (1):
> >   thunderbolt: Poll 10ms for REG_FW_STS_NVM_AUTH_DONE to be set
> >
> > Mika Westerberg (3):
> >   thunderbolt: Bond lanes only when dual_link_port != NULL in alloc_dev_default()
> >   thunderbolt: Add device links only when software connection manager is used
> >   thunderbolt: No need to include <linux/acpi.h> in usb4_port.c
> >
> >  drivers/thunderbolt/icm.c       | 20 ++++++----
> >  drivers/thunderbolt/nhi.c       | 71 ++-------------------------------
> >  drivers/thunderbolt/nhi.h       |  2 +
> >  drivers/thunderbolt/tb.c        | 67 +++++++++++++++++++++++++++++++
> >  drivers/thunderbolt/test.c      | 22 +++++-----
> >  drivers/thunderbolt/usb4_port.c |  1 -
> >  6 files changed, 97 insertions(+), 86 deletions(-)
> >
> 
>  Reviewed-by: Yehezkel Bernat <YehezkelShB@gmail.com>

Thanks!

Applied all to thunderbolt.git/next.

      reply	other threads:[~2021-06-11  8:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 11:00 [PATCH 0/5] thunderbolt: Support for Intel Alder Lake and improvements Mika Westerberg
2021-06-07 11:00 ` [PATCH 1/5] thunderbolt: Bond lanes only when dual_link_port != NULL in alloc_dev_default() Mika Westerberg
2021-06-07 11:00 ` [PATCH 2/5] thunderbolt: Add device links only when software connection manager is used Mika Westerberg
2021-06-07 11:00 ` [PATCH 3/5] thunderbolt: Poll 10ms for REG_FW_STS_NVM_AUTH_DONE to be set Mika Westerberg
2021-06-07 11:00 ` [PATCH 4/5] thunderbolt: No need to include <linux/acpi.h> in usb4_port.c Mika Westerberg
2021-06-07 11:00 ` [PATCH 5/5] thunderbolt: Add support for Intel Alder Lake Mika Westerberg
2021-06-07 11:52 ` [PATCH 0/5] thunderbolt: Support for Intel Alder Lake and improvements Yehezkel Bernat
2021-06-11  8:46   ` 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=YMMizWEKEqqxPet5@lahna \
    --to=mika.westerberg@linux.intel.com \
    --cc=andreas.noever@gmail.com \
    --cc=azhar.shaikh@intel.com \
    --cc=dan.carpenter@oracle.com \
    --cc=gil.fine@intel.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lukas@wunner.de \
    --cc=michael.jamet@intel.com \
    --cc=yehezkelshb@gmail.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