From: Tianfei Zhang <tianfei.zhang@intel.com>
To: hao.wu@intel.com, trix@redhat.com, mdf@kernel.org,
yilun.xu@intel.com, linux-fpga@vger.kernel.org,
linux-doc@vger.kernel.org
Cc: corbet@lwn.net, rdunlap@infradead.org,
Tianfei Zhang <tianfei.zhang@intel.com>
Subject: [PATCH v5 0/2] check feature type for DFL irq parsing
Date: Wed, 23 Mar 2022 04:51:00 -0400 [thread overview]
Message-ID: <20220323085102.2297964-1-tianfei.zhang@intel.com> (raw)
This patch set adds an extended usage of Feature ID for DFL.
Previously the feature IDs defined are unique, no matter
which feature type. But currently we want to extend its
usage to have a per-type feature ID space.
Patch 1 adds feature type checking before parse the irq info.
Patch 2 adds description about the Feature ID.
v5:
- Fix documentation from Matthew's comment.
v4:
- Fix the git commit from Hao's comments.
- Split documentation into another patch.
v3:
- Remove "Fixes" in commit log with Hao's comment, this is a
extension not a bug fix.
v2:
- add DFL Feature ID Registry in documentation.
Tianfei zhang (2):
fpga: dfl: check feature type before parse irq info
Documentation: fpga: dfl: add description of Feature ID
Documentation/fpga/dfl.rst | 10 ++++++++++
drivers/fpga/dfl.c | 38 ++++++++++++++++++++++----------------
2 files changed, 32 insertions(+), 16 deletions(-)
--
2.26.2
next reply other threads:[~2022-03-23 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 8:51 Tianfei Zhang [this message]
2022-03-23 8:51 ` [PATCH v5 1/2] fpga: dfl: check feature type before parse irq info Tianfei Zhang
2022-03-23 17:47 ` matthew.gerlach
2022-03-23 8:51 ` [PATCH v5 2/2] Documentation: fpga: dfl: add description of Feature ID Tianfei Zhang
2022-03-23 12:12 ` Bagas Sanjaya
2022-03-24 3:02 ` Zhang, Tianfei
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=20220323085102.2297964-1-tianfei.zhang@intel.com \
--to=tianfei.zhang@intel.com \
--cc=corbet@lwn.net \
--cc=hao.wu@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=rdunlap@infradead.org \
--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).