From: matthew.gerlach@linux.intel.com
To: hao.wu@intel.com, yilun.xu@intel.com, russell.h.weight@intel.com,
basheer.ahmed.muddebihal@intel.com, trix@redhat.com,
mdf@kernel.org, corbet@lwn.net, linux-fpga@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
dan.j.williams@intel.com, ashok.raj@intel.com,
tianfei.zhang@intel.com
Cc: Matthew Gerlach <matthew.gerlach@linux.intel.com>
Subject: [PATCH v2 0/2] Add PCIE device IDs for Intel DFL cards
Date: Wed, 2 Mar 2022 16:35:32 -0800 [thread overview]
Message-ID: <20220303003534.3307971-1-matthew.gerlach@linux.intel.com> (raw)
From: Matthew Gerlach <matthew.gerlach@linux.intel.com>
This patch set adds the PCIE device IDs for Intel cards with Device Feature
Lists (DFL) to the pci_dev_table for the dfl-pci driver. This patch set
was separated for clarity from a larger patch set submitted by
tianfei.zhang@intel.com.
Patch 1 adds documentation about identifying PCIE FPGA cards
with Device Feature Lists (DFL).
Patch 2 adds the device ids to the pci_dev_table for the dfl-pci driver.
Matthew Gerlach (2):
Documentation: fpga: dfl: add PCI Identification documentation
drivers: fpga: dfl-pci: Add PCIE device IDs for Intel DFL cards
Documentation/fpga/dfl.rst | 20 ++++++++++++++++++++
drivers/fpga/dfl-pci.c | 4 ++++
2 files changed, 24 insertions(+)
--
2.25.1
next reply other threads:[~2022-03-03 0:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 0:35 matthew.gerlach [this message]
2022-03-03 0:35 ` [PATCH v2 1/2] Documentation: fpga: dfl: add PCI Identification documentation matthew.gerlach
2022-03-03 22:04 ` Tom Rix
2022-03-04 16:45 ` Russ Weight
2022-03-04 18:30 ` matthew.gerlach
2022-03-22 17:11 ` Tom Rix
2022-03-11 4:16 ` Wu, Hao
2022-03-03 0:35 ` [PATCH v2 2/2] drivers: fpga: dfl-pci: Add PCIE device IDs for Intel DFL cards matthew.gerlach
2022-03-11 4:20 ` Wu, Hao
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=20220303003534.3307971-1-matthew.gerlach@linux.intel.com \
--to=matthew.gerlach@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=basheer.ahmed.muddebihal@intel.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=hao.wu@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=russell.h.weight@intel.com \
--cc=tianfei.zhang@intel.com \
--cc=trix@redhat.com \
--cc=yilun.xu@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).