From: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
To: Uma Krishnan <ukrishn@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id.au,
Ian Munsie <imunsie@au1.ibm.com>
Cc: "Matthew R. Ochs" <mrochs@linux.vnet.ibm.com>,
Christophe Lombard <clombard@linux.vnet.ibm.com>,
Andrew Donnellan <andrew.donnellan@au1.ibm.com>
Subject: Re: [PATCH] cxl: Enable PCI device ID for future IBM CXL adapter
Date: Wed, 22 Feb 2017 15:44:04 +0100 [thread overview]
Message-ID: <c4d059e9-c7b0-29f2-f2db-c9d76cb84497@linux.vnet.ibm.com> (raw)
In-Reply-To: <1487303123-7835-1-git-send-email-ukrishn@linux.vnet.ibm.com>
Le 17/02/2017 à 04:45, Uma Krishnan a écrit :
> From: "Matthew R. Ochs" <mrochs@linux.vnet.ibm.com>
>
> Add support for a future IBM Coherent Accelerator (CXL) device
> with an ID of 0x0623.
>
> Signed-off-by: Matthew R. Ochs <mrochs@linux.vnet.ibm.com>
> Signed-off-by: Uma Krishnan <ukrishn@linux.vnet.ibm.com>
> ---
Acked-by: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
> drivers/misc/cxl/pci.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/misc/cxl/pci.c b/drivers/misc/cxl/pci.c
> index cca9388..16d858f 100644
> --- a/drivers/misc/cxl/pci.c
> +++ b/drivers/misc/cxl/pci.c
> @@ -123,6 +123,7 @@ static const struct pci_device_id cxl_pci_tbl[] = {
> { PCI_DEVICE(PCI_VENDOR_ID_IBM, 0x044b), },
> { PCI_DEVICE(PCI_VENDOR_ID_IBM, 0x04cf), },
> { PCI_DEVICE(PCI_VENDOR_ID_IBM, 0x0601), },
> + { PCI_DEVICE(PCI_VENDOR_ID_IBM, 0x0623), },
> { PCI_DEVICE_CLASS(0x120000, ~0), },
>
> { }
>
next prev parent reply other threads:[~2017-02-22 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 3:45 [PATCH] cxl: Enable PCI device ID for future IBM CXL adapter Uma Krishnan
2017-02-19 10:54 ` Andrew Donnellan
2017-02-21 20:07 ` Uma Krishnan
2017-02-22 14:44 ` Frederic Barrat [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-07 22:03 Uma Krishnan
2015-12-07 22:19 ` Ian Munsie
2015-12-07 23:05 ` Matthew R. Ochs
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=c4d059e9-c7b0-29f2-f2db-c9d76cb84497@linux.vnet.ibm.com \
--to=fbarrat@linux.vnet.ibm.com \
--cc=andrew.donnellan@au1.ibm.com \
--cc=clombard@linux.vnet.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=mrochs@linux.vnet.ibm.com \
--cc=ukrishn@linux.vnet.ibm.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).