From: "Levy, Amir (Jer)" <amir.jer.levy@intel.com>
To: Andreas Noever <andreas.noever@gmail.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
thunderbolt-linux <thunderbolt-linux@intel.com>,
"Westerberg, Mika" <mika.westerberg@intel.com>,
"Winkler, Tomas" <tomas.winkler@intel.com>
Subject: RE: [PATCH v2 0/8] thunderbolt: Introducing Thunderbolt(TM) networking
Date: Wed, 13 Jul 2016 06:14:12 +0000 [thread overview]
Message-ID: <E607265CB020454880711A6F96C05A03893CB823@hasmsx107.ger.corp.intel.com> (raw)
In-Reply-To: <CAMxnaaWB2SR-d=JV3njmrbeCjE30DNFQ5YLXy748hjYZPayXWw@mail.gmail.com>
On Wed, Jul 13 2016, 01:19 AM, Andreas Noever wrote:
> Since this is now a separate driver I would prefer if it was in a different
> (sub)directory (maybe thunderbolt/icm?).
>
Thanks Andreas for the comment, will change it in the next patch.
Any more comments?
prev parent reply other threads:[~2016-07-13 6:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 8:35 [PATCH v2 0/8] thunderbolt: Introducing Thunderbolt(TM) networking Amir Levy
2016-06-29 8:35 ` [PATCH v2 1/8] thunderbolt: Macro rename Amir Levy
2016-06-29 8:35 ` [PATCH v2 2/8] thunderbolt: Updating device IDs Amir Levy
2016-06-29 8:35 ` [PATCH v2 3/8] thunderbolt: Updating the register definitions Amir Levy
2016-06-29 8:35 ` [PATCH v2 4/8] thunderbolt: Kconfig for Thunderbolt(TM) networking Amir Levy
2016-06-29 8:35 ` [PATCH v2 5/8] thunderbolt: Communication with the ICM (firmware) Amir Levy
2016-06-29 8:35 ` [PATCH v2 6/8] thunderbolt: Networking state machine Amir Levy
2016-06-29 8:35 ` [PATCH v2 7/8] thunderbolt: Networking transmit and receive Amir Levy
2016-06-29 8:35 ` [PATCH v2 8/8] thunderbolt: Networking doc Amir Levy
2016-07-12 10:50 ` [PATCH v2 0/8] thunderbolt: Introducing Thunderbolt(TM) networking Levy, Amir (Jer)
2016-07-12 22:19 ` Andreas Noever
2016-07-13 6:14 ` Levy, Amir (Jer) [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=E607265CB020454880711A6F96C05A03893CB823@hasmsx107.ger.corp.intel.com \
--to=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 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).