From: Greg KH <gregkh@linuxfoundation.org>
To: Amir Levy <amir.jer.levy@intel.com>
Cc: andreas.noever@gmail.com, bhelgaas@google.com,
linux-pci@vger.kernel.org, michael.jamet@intel.com,
dan.alloun@intel.com, mika.westerberg@intel.com,
kai.svahn@intel.com, andriy.shevchenko@intel.com,
tomas.winkler@intel.com
Subject: Re: [PATCH 1/6] thunderbolt: Updating the register definitions
Date: Mon, 23 May 2016 07:40:06 -0700 [thread overview]
Message-ID: <20160523144006.GA28980@kroah.com> (raw)
In-Reply-To: <1463993336-2750-2-git-send-email-amir.jer.levy@intel.com>
On Mon, May 23, 2016 at 11:48:51AM +0300, Amir Levy wrote:
> --- a/include/linux/pci_ids.h
> +++ b/include/linux/pci_ids.h
> @@ -2618,6 +2618,8 @@
> #define PCI_DEVICE_ID_INTEL_FALCON_RIDGE_2C_BRIDGE 0x156b
> #define PCI_DEVICE_ID_INTEL_FALCON_RIDGE_4C_NHI 0x156c
> #define PCI_DEVICE_ID_INTEL_FALCON_RIDGE_4C_BRIDGE 0x156d
> +#define PCI_DEVICE_ID_INTEL_WIN_RIDGE_2C_NHI 0x157d
> +#define PCI_DEVICE_ID_INTEL_WIN_RIDGE_2C_BRIDGE 0x157e
> #define PCI_DEVICE_ID_INTEL_ALPINE_RIDGE_2C_NHI 0x1575 /* Thunderbolt 3 */
> #define PCI_DEVICE_ID_INTEL_ALPINE_RIDGE_2C_BRIDGE 0x1576
> #define PCI_DEVICE_ID_INTEL_ALPINE_RIDGE_4C_NHI 0x1577
Please read the top of this file for why you shouldn't be adding new
ids to it.
next prev parent reply other threads:[~2016-05-23 14:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 8:48 [PATCH 0/6] thunderbolt: Introducing Thunderbolt(TM) networking Amir Levy
2016-05-23 8:48 ` [PATCH 1/6] thunderbolt: Updating the register definitions Amir Levy
2016-05-23 10:10 ` Shevchenko, Andriy
2016-05-24 10:06 ` Lukas Wunner
2016-05-23 14:40 ` Greg KH [this message]
2016-05-24 9:48 ` Levy, Amir (Jer)
2016-05-23 8:48 ` [PATCH 2/6] thunderbolt: Communication with the ICM (firmware) Amir Levy
2016-05-23 10:33 ` Andy Shevchenko
2016-05-23 8:48 ` [PATCH 3/6] thunderbolt: Networking state machine Amir Levy
2016-05-23 8:48 ` [PATCH 4/6] thunderbolt: Networking transmit and receive Amir Levy
2016-05-23 8:48 ` [PATCH 5/6] thunderbolt: Kconfig for Thunderbolt(TM) networking Amir Levy
2016-05-23 8:48 ` [PATCH 6/6] thunderbolt: Networking doc Amir Levy
2016-05-23 15:34 ` Greg KH
2016-05-24 9:54 ` Levy, Amir (Jer)
2016-05-24 14:41 ` Greg KH
2016-05-24 10:55 ` [PATCH 0/6] thunderbolt: Introducing Thunderbolt(TM) networking Lukas Wunner
2016-05-24 13:58 ` Levy, Amir (Jer)
2016-05-24 23:24 ` Andreas Noever
2016-06-01 12:22 ` Levy, Amir (Jer)
2016-06-08 17:00 ` Andreas Noever
2016-06-09 12:53 ` Levy, Amir (Jer)
2016-06-14 19:22 ` Andreas Noever
2016-11-09 13:11 ` Lukas Wunner
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=20160523144006.GA28980@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amir.jer.levy@intel.com \
--cc=andreas.noever@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=bhelgaas@google.com \
--cc=dan.alloun@intel.com \
--cc=kai.svahn@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@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.