From: Greg KH <gregkh@linuxfoundation.org>
To: David Miller <davem@davemloft.net>
Cc: amir.jer.levy@intel.com, andreas.noever@gmail.com,
bhelgaas@google.com, corbet@lwn.net,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
mario_limonciello@dell.com, thunderbolt-linux@intel.com,
mika.westerberg@intel.com, tomas.winkler@intel.com,
xiong.y.zhang@intel.com
Subject: Re: [PATCH v8 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking
Date: Fri, 30 Sep 2016 08:30:05 +0200 [thread overview]
Message-ID: <20160930063005.GA7571@kroah.com> (raw)
In-Reply-To: <20160930.015555.2177533749954623343.davem@davemloft.net>
On Fri, Sep 30, 2016 at 01:55:55AM -0400, David Miller wrote:
> From: Amir Levy <amir.jer.levy@intel.com>
> Date: Wed, 28 Sep 2016 17:44:22 +0300
>
> > This driver enables Thunderbolt Networking on non-Apple platforms
> > running Linux.
>
> Greg, any idea where this should get merged once fully vetted? I can
> take it through the net-next tree, but I'm fine with another more
> appropriate tree taking it as well.
I am supposed to be taking thunderbolt patches, but if this really is a
network driver, it should go under drivers/net/ somewhere. It needs
more review though, it's not ready to go through anyone's tree just yet :)
I'll let the thunderbolt maintainer go through it first before asking
for a netdev review.
thanks,
greg k-h
next prev parent reply other threads:[~2016-09-30 6:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 14:44 [PATCH v8 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking Amir Levy
2016-09-28 14:44 ` [PATCH v8 1/8] thunderbolt: Macro rename Amir Levy
2016-09-28 14:44 ` [PATCH v8 2/8] thunderbolt: Updating the register definitions Amir Levy
2016-09-28 14:44 ` [PATCH v8 3/8] thunderbolt: Communication with the ICM (firmware) Amir Levy
2016-12-02 1:21 ` Andy Lutomirski
2016-12-19 12:24 ` Mika Westerberg
2016-12-19 17:21 ` Mario.Limonciello
2016-12-19 17:21 ` Mario.Limonciello
2016-12-20 8:09 ` Mika Westerberg
2016-09-28 14:44 ` [PATCH v8 4/8] thunderbolt: Networking state machine Amir Levy
2016-09-28 14:44 ` [PATCH v8 5/8] thunderbolt: Networking transmit and receive Amir Levy
2016-09-28 14:44 ` [PATCH v8 6/8] thunderbolt: Kconfig for Thunderbolt Networking Amir Levy
2016-09-28 14:44 ` [PATCH v8 7/8] thunderbolt: Networking doc Amir Levy
2016-09-28 14:44 ` [PATCH v8 8/8] thunderbolt: Adding maintainer entry Amir Levy
2016-09-30 5:55 ` [PATCH v8 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking David Miller
2016-09-30 6:30 ` Greg KH [this message]
2016-09-30 6:40 ` David Miller
2016-09-30 8:37 ` Levy, Amir (Jer)
2016-09-30 8:50 ` gregkh
2016-10-21 14:57 ` Mario.Limonciello
2016-10-21 14:57 ` Mario.Limonciello
2016-10-27 15:51 ` 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=20160930063005.GA7571@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amir.jer.levy@intel.com \
--cc=andreas.noever@gmail.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mario_limonciello@dell.com \
--cc=mika.westerberg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=thunderbolt-linux@intel.com \
--cc=tomas.winkler@intel.com \
--cc=xiong.y.zhang@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.