From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Levy, Amir (Jer)" <amir.jer.levy@intel.com>
Cc: Simon Guinot <simon.guinot@sequanux.org>,
"andreas.noever@gmail.com" <andreas.noever@gmail.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"mario_limonciello@dell.com" <mario_limonciello@dell.com>,
thunderbolt-linux <thunderbolt-linux@intel.com>,
"Westerberg, Mika" <mika.westerberg@intel.com>,
"Winkler, Tomas" <tomas.winkler@intel.com>,
"Zhang, Xiong Y" <xiong.y.zhang@intel.com>,
"Jamet, Michael" <michael.jamet@intel.com>,
"remi.rerolle@seagate.com" <remi.rerolle@seagate.com>
Subject: Re: [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking
Date: Mon, 21 Nov 2016 13:22:41 +0100 [thread overview]
Message-ID: <20161121122241.GA16158@kroah.com> (raw)
In-Reply-To: <E607265CB020454880711A6F96C05A03BE2214E2@hasmsx107.ger.corp.intel.com>
On Sun, Nov 20, 2016 at 06:30:19AM +0000, Levy, Amir (Jer) wrote:
> On Fri, Nov 18 2016, 12:07 PM, gregkh@linuxfoundation.org wrote:
> > On Fri, Nov 18, 2016 at 08:48:36AM +0000, Levy, Amir (Jer) wrote:
> > > > BTW, it is quite a shame that the Thunderbolt firmware version can't
> > > > be read from Linux.
> > > >
> > >
> > > This is WIP, once this patch will be upstream, we will be able to
> > > focus more on aligning Linux with the Thunderbolt features that we have
> > for windows.
> >
> > Why is this patch somehow holding that work back? You aren't just sitting
> > around waiting for people to review this and not doing anything else, right?
> > Is there some basic building block in these patches that your firmware
> > download code is going to rely on?
> >
> > confused,
> >
> > greg k-h
>
> All the Thunderbolt SW features (including networking and FW update) depend
> on the communication with FW, which is patch 3/8 in the series.
> The patch also sets up a generic netlink for user space communication.
It's that "generic netlink" connection that I really want a whole lot of
revewers to read over as it's very unusual and "different" from all
other driver subsystems.
thanks,
greg k-h
next prev parent reply other threads:[~2016-11-21 12:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 14:20 [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking Amir Levy
2016-11-09 14:20 ` [PATCH v9 1/8] thunderbolt: Macro rename Amir Levy
2016-11-09 14:20 ` [PATCH v9 2/8] thunderbolt: Updating the register definitions Amir Levy
2016-11-09 14:20 ` [PATCH v9 3/8] thunderbolt: Communication with the ICM (firmware) Amir Levy
2016-11-09 14:20 ` [PATCH v9 4/8] thunderbolt: Networking state machine Amir Levy
2016-11-09 14:20 ` [PATCH v9 5/8] thunderbolt: Networking transmit and receive Amir Levy
2016-11-09 14:20 ` [PATCH v9 6/8] thunderbolt: Kconfig for Thunderbolt Networking Amir Levy
2016-11-09 14:20 ` [PATCH v9 7/8] thunderbolt: Networking doc Amir Levy
2016-11-09 16:00 ` Greg KH
2016-11-10 11:47 ` Levy, Amir (Jer)
2016-11-10 11:53 ` Greg KH
2016-11-10 14:24 ` Jonathan Corbet
2016-11-09 14:20 ` [PATCH v9 8/8] thunderbolt: Adding maintainer entry Amir Levy
2016-11-09 14:36 ` [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking Simon Guinot
2016-11-09 15:42 ` Levy, Amir (Jer)
2016-11-15 10:59 ` Simon Guinot
2016-11-18 8:48 ` Levy, Amir (Jer)
2016-11-18 10:07 ` gregkh
2016-11-20 6:30 ` Levy, Amir (Jer)
2016-11-21 12:22 ` gregkh [this message]
2016-11-18 11:20 ` Simon Guinot
2016-11-22 17:28 ` Simon Guinot
2016-11-22 17:36 ` Mario.Limonciello
2016-11-22 17:36 ` Mario.Limonciello
2016-11-24 20:35 ` Levy, Amir (Jer)
2016-11-09 16:02 ` Greg KH
2016-11-10 11:39 ` Levy, Amir (Jer)
2016-11-10 11:44 ` Greg KH
2016-11-10 11:48 ` Levy, Amir (Jer)
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=20161121122241.GA16158@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=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mario_limonciello@dell.com \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=remi.rerolle@seagate.com \
--cc=simon.guinot@sequanux.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.