All of lore.kernel.org
 help / color / mirror / Atom feed
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
Cc: linux-doc@vger.kernel.org, corbet@lwn.net,
	Tianfei Zhang <tianfei.zhang@intel.com>
Subject: [PATCH v7 0/2] check feature type for DFL irq parsing
Date: Mon, 18 Apr 2022 23:29:40 -0400	[thread overview]
Message-ID: <20220419032942.427429-1-tianfei.zhang@intel.com> (raw)

This patch set adds an extended usage of Feature ID for DFL 
and based on 5.18-rc2. 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 link address about the Feature ID table.

v7:
  - Add reviewed-by from Matthew Gerlach and Acked-by from Hao. 
  - Change title and git commit message for patch 2. 
v6:
  - Fix documentation from Hao's comment. 
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 link address of feature id table

 Documentation/fpga/dfl.rst |  5 +++++
 drivers/fpga/dfl.c         | 38 ++++++++++++++++++++++----------------
 2 files changed, 27 insertions(+), 16 deletions(-)

-- 
2.26.2


             reply	other threads:[~2022-04-19  3:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19  3:29 Tianfei Zhang [this message]
2022-04-19  3:29 ` [PATCH v7 1/2] fpga: dfl: check feature type before parse irq info Tianfei Zhang
2022-04-21 14:46   ` Moritz Fischer
2022-04-25  7:31     ` Xu Yilun
2022-04-19  3:29 ` [PATCH v7 2/2] Documentation: fpga: dfl: add link address of feature id table Tianfei Zhang
2022-04-21 14:47   ` Moritz Fischer
2022-04-25  7:23     ` Xu Yilun
2022-04-26  2:15       ` 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=20220419032942.427429-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=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 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.