linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yehezkel Bernat <yehezkelshb@gmail.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andreas Noever <andreas.noever@gmail.com>,
	michael.jamet@intel.com, lukas@wunner.de,
	anthony.wong@canonical.com
Subject: Re: [PATCH v2 0/4] thunderbolt: Miscellaneous cleanups
Date: Thu, 20 Sep 2018 13:33:19 +0300	[thread overview]
Message-ID: <CA+CmpXvX2iOhc4eR2mTK1V+5p_w0UbpkVOR+Fv8JkadnD8t1TQ@mail.gmail.com> (raw)
In-Reply-To: <20180917144334.18367-1-mika.westerberg@linux.intel.com>

On Mon, Sep 17, 2018 at 5:43 PM Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:
>
> Hi all,
>
> Here are a couple of changes which have been in my TODO list some time
> already but have not had time to make a proper patch out of them until now.
>
> The only change to the previous version is that I realized it could be
> useful for users to see the actual connected devices (including their name
> which is read from DROM) printed to the system log. Hence the patch 2/4.
>
> Mika Westerberg (4):
>   thunderbolt: Make the driver less verbose
>   thunderbolt: Print connected devices
>   thunderbolt: Convert rest of the driver files to use SPDX identifier
>   thunderbolt: Add Intel as copyright holder
>
>  drivers/thunderbolt/cap.c      |  3 +-
>  drivers/thunderbolt/ctl.c      |  9 +++--
>  drivers/thunderbolt/ctl.h      |  3 +-
>  drivers/thunderbolt/dma_port.c |  5 +--
>  drivers/thunderbolt/dma_port.h |  5 +--
>  drivers/thunderbolt/domain.c   |  7 +---
>  drivers/thunderbolt/eeprom.c   |  5 ++-
>  drivers/thunderbolt/icm.c      |  5 +--
>  drivers/thunderbolt/nhi.c      | 33 ++++++++--------
>  drivers/thunderbolt/nhi.h      |  3 +-
>  drivers/thunderbolt/nhi_regs.h |  1 +
>  drivers/thunderbolt/path.c     | 26 ++++++-------
>  drivers/thunderbolt/property.c |  5 +--
>  drivers/thunderbolt/switch.c   | 71 +++++++++++++++++++---------------
>  drivers/thunderbolt/tb.c       | 10 ++---
>  drivers/thunderbolt/tb.h       |  9 +++--
>  drivers/thunderbolt/tb_msgs.h  |  5 +--
>  drivers/thunderbolt/tb_regs.h  |  3 +-
>  drivers/thunderbolt/xdomain.c  |  5 +--
>  include/linux/thunderbolt.h    |  5 +--
>  20 files changed, 107 insertions(+), 111 deletions(-)
>
> --
> 2.18.0
>

Acked-by: Yehezkel Bernat <yehezkelshb@gmail.com>

  parent reply	other threads:[~2018-09-20 10:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-17 14:43 [PATCH v2 0/4] thunderbolt: Miscellaneous cleanups Mika Westerberg
2018-09-17 14:43 ` [PATCH v2 1/4] thunderbolt: Make the driver less verbose Mika Westerberg
2018-09-17 14:43 ` [PATCH v2 2/4] thunderbolt: Print connected devices Mika Westerberg
2018-09-17 14:43 ` [PATCH v2 3/4] thunderbolt: Convert rest of the driver files to use SPDX identifier Mika Westerberg
2018-09-17 14:43 ` [PATCH v2 4/4] thunderbolt: Add Intel as copyright holder Mika Westerberg
2018-09-20 10:33 ` Yehezkel Bernat [this message]
2018-09-21  8:28   ` [PATCH v2 0/4] thunderbolt: Miscellaneous cleanups 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=CA+CmpXvX2iOhc4eR2mTK1V+5p_w0UbpkVOR+Fv8JkadnD8t1TQ@mail.gmail.com \
    --to=yehezkelshb@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=anthony.wong@canonical.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 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).