linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Amir Levy <amir.jer.levy@intel.com>
Cc: 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 v7 3/8] thunderbolt: Kconfig for Thunderbolt Networking
Date: Tue, 27 Sep 2016 16:00:44 +0200	[thread overview]
Message-ID: <20160927140044.GA21133@kroah.com> (raw)
In-Reply-To: <1474983821-2313-4-git-send-email-amir.jer.levy@intel.com>

On Tue, Sep 27, 2016 at 04:43:36PM +0300, Amir Levy wrote:
> Update to the Kconfig Thunderbolt description to add
> Thunderbolt networking as an option.
> The menu item "Thunderbolt support" now offers:
> "Apple Hardware Support" (existing)
>         and/or
> "Thunderbolt Networking" (new)
> 
> You can choose the driver for your platform or build both drivers -
> each driver will detect if it can run on the specific platform.
> If the Thunderbolt Networking option is chosen, Thunderbolt Networking
> will be enabled between Linux non-Apple systems, macOS and
> Windows based systems.
> Thunderbolt Networking will not affect any other Thunderbolt feature that
> was previous available to Linux users on either Apple or
> non-Apple platforms.
> 
> Signed-off-by: Amir Levy <amir.jer.levy@intel.com>
> ---
>  drivers/thunderbolt/Kconfig  | 27 +++++++++++++++++++++++----
>  drivers/thunderbolt/Makefile |  2 +-
>  2 files changed, 24 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/thunderbolt/Kconfig b/drivers/thunderbolt/Kconfig
> index c121acc..376e5bb 100644
> --- a/drivers/thunderbolt/Kconfig
> +++ b/drivers/thunderbolt/Kconfig
> @@ -1,13 +1,32 @@
> -menuconfig THUNDERBOLT
> -	tristate "Thunderbolt support for Apple devices"
> +config THUNDERBOLT
> +	tristate "Thunderbolt support"
>  	depends on PCI
>  	select CRC32
>  	help
> -	  Cactus Ridge Thunderbolt Controller driver
> +	  Thunderbolt Controller driver
> +
> +if THUNDERBOLT
> +
> +config THUNDERBOLT_APPLE
> +	tristate "Apple hardware support"
> +	help
>  	  This driver is required if you want to hotplug Thunderbolt devices on
>  	  Apple hardware.
>  
>  	  Device chaining is currently not supported.
>  
> -	  To compile this driver a module, choose M here. The module will be
> +	  To compile this driver as a module, choose M here. The module will be
>  	  called thunderbolt.
> +
> +config THUNDERBOLT_ICM

You are adding a config option here that is not used in the tree yet.
Please wait until you need the option to actually add it :)

You might just want to do the APPLE stuff here, that way you can drop in
the networking stuff in a simple patch at the end of this series.

thanks,

greg k-h

  reply	other threads:[~2016-09-27 14:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27 13:43 [PATCH v7 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking Amir Levy
2016-09-27 13:43 ` [PATCH v7 1/8] thunderbolt: Macro rename Amir Levy
2016-09-27 13:43 ` [PATCH v7 2/8] thunderbolt: Updating the register definitions Amir Levy
2016-09-27 13:43 ` [PATCH v7 3/8] thunderbolt: Kconfig for Thunderbolt Networking Amir Levy
2016-09-27 14:00   ` Greg KH [this message]
2016-09-27 13:43 ` [PATCH v7 4/8] thunderbolt: Communication with the ICM (firmware) Amir Levy
2016-09-27 14:11   ` Greg KH
2016-09-27 13:43 ` [PATCH v7 5/8] thunderbolt: Networking state machine Amir Levy
2016-09-27 14:13   ` Greg KH
2016-09-27 14:15   ` Greg KH
2016-09-27 13:43 ` [PATCH v7 6/8] thunderbolt: Networking transmit and receive Amir Levy
2016-09-27 13:43 ` [PATCH v7 7/8] thunderbolt: Networking doc Amir Levy
2016-09-27 13:43 ` [PATCH v7 8/8] thunderbolt: Adding maintainer entry Amir Levy

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=20160927140044.GA21133@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=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 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).