All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Amir Levy <amir.jer.levy@intel.com>,
	andreas.noever@gmail.com, gregkh@linuxfoundation.org,
	bhelgaas@google.com
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, thunderbolt-linux@intel.com,
	mika.westerberg@intel.com, tomas.winkler@intel.com
Subject: Re: [PATCH v4 0/7] thunderbolt: Introducing Thunderbolt(TM) networking
Date: Tue, 19 Jul 2016 10:14:05 -0700	[thread overview]
Message-ID: <1468948445.1900.53.camel@perches.com> (raw)
In-Reply-To: <1468836040-28043-1-git-send-email-amir.jer.levy@intel.com>

On Mon, 2016-07-18 at 13:00 +0300, Amir Levy wrote:
> This is version 4 of Thunderbolt(TM) driver for non-Apple hardware.
[]
>  Documentation/00-INDEX                   |    2 +
>  Documentation/thunderbolt-networking.txt |  135 ++
>  drivers/thunderbolt/Kconfig              |   25 +-
>  drivers/thunderbolt/Makefile             |    3 +-
>  drivers/thunderbolt/icm/Makefile         |   28 +
>  drivers/thunderbolt/icm/icm_nhi.c        | 1642 +++++++++++++++++++++
>  drivers/thunderbolt/icm/icm_nhi.h        |   93 ++
>  drivers/thunderbolt/icm/net.c            | 2276 ++++++++++++++++++++++++++++++
>  drivers/thunderbolt/icm/net.h            |  274 ++++
>  drivers/thunderbolt/nhi_regs.h           |  115 +-
>  10 files changed, 4585 insertions(+), 8 deletions(-)
>  create mode 100644 Documentation/thunderbolt-networking.txt
>  create mode 100644 drivers/thunderbolt/icm/Makefile
>  create mode 100644 drivers/thunderbolt/icm/icm_nhi.c
>  create mode 100644 drivers/thunderbolt/icm/icm_nhi.h
>  create mode 100644 drivers/thunderbolt/icm/net.c
>  create mode 100644 drivers/thunderbolt/icm/net.h

Is a MAINTAINERS update necessary or is Andreas going to
be the maintainer?

  parent reply	other threads:[~2016-07-19 17:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18 10:00 [PATCH v4 0/7] thunderbolt: Introducing Thunderbolt(TM) networking Amir Levy
2016-07-18 10:00 ` [PATCH v4 1/7] thunderbolt: Macro rename Amir Levy
2016-07-18 10:00 ` [PATCH v4 2/7] thunderbolt: Updating the register definitions Amir Levy
2016-07-26  7:39   ` Andreas Noever
2016-07-26  9:08     ` Levy, Amir (Jer)
2016-07-26  9:08       ` Levy, Amir (Jer)
2016-07-18 10:00 ` [PATCH v4 3/7] thunderbolt: Kconfig for Thunderbolt(TM) networking Amir Levy
2016-07-18 10:00 ` [PATCH v4 4/7] thunderbolt: Communication with the ICM (firmware) Amir Levy
2016-07-18 10:00 ` [PATCH v4 5/7] thunderbolt: Networking state machine Amir Levy
2016-07-24 22:36   ` Lukas Wunner
2016-07-27  7:30     ` Levy, Amir (Jer)
2016-07-18 10:00 ` [PATCH v4 6/7] thunderbolt: Networking transmit and receive Amir Levy
2016-07-18 10:00 ` [PATCH v4 7/7] thunderbolt: Networking doc Amir Levy
2016-07-19 17:14 ` Joe Perches [this message]
2016-07-20  6:02   ` [PATCH v4 0/7] thunderbolt: Introducing Thunderbolt(TM) networking Levy, Amir (Jer)
2016-07-20  6:32     ` Joe Perches
2016-07-19 22:02 ` Bjorn Helgaas
2016-07-26  7:35   ` Andreas Noever

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=1468948445.1900.53.camel@perches.com \
    --to=joe@perches.com \
    --cc=amir.jer.levy@intel.com \
    --cc=andreas.noever@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mika.westerberg@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=thunderbolt-linux@intel.com \
    --cc=tomas.winkler@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.