public inbox for linux-cxl@vger.kernel.org
 help / color / mirror / Atom feed
From: Yanfei Xu <yanfei.xu@intel.com>
To: linux-cxl@vger.kernel.org
Cc: dave@stgolabs.net, jonathan.cameron@huawei.com,
	dave.jiang@intel.com, alison.schofield@intel.com,
	vishal.l.verma@intel.com, ira.weiny@intel.com,
	dan.j.williams@intel.com, ming4.li@intel.com,
	yanfei.xu@intel.com
Subject: [v2 0/4] Fixes for hdm docoder initialization from DVSEC ranges
Date: Fri,  9 Aug 2024 17:34:38 +0800	[thread overview]
Message-ID: <20240809093442.646545-1-yanfei.xu@intel.com> (raw)

The first three patches are functional fixes, the fourth one is for adjustment
of code format.

v1:https://lore.kernel.org/linux-cxl/66b4db4ff3730_c144829418@dwillia2-xfh.jf.intel.com.notmuch/T/#t

v1->v2:
  separate one big patch into four.


Yanfei Xu (4):
  cxl/pci: Fix to record only non-zero ranges
  cxl/pci: Don't set up decoders for disallowed DVSEC ranges
  cxl/pci: Check Mem_info_valid bit for each applicable DVSEC range
  cxl/pci: Simplify the code logic of cxl_hdm_decode_init

 drivers/cxl/core/pci.c        | 114 ++++++++++++----------------------
 drivers/cxl/cxl.h             |   2 +-
 drivers/cxl/port.c            |   2 +-
 tools/testing/cxl/test/mock.c |   4 +-
 4 files changed, 42 insertions(+), 80 deletions(-)

-- 
2.39.2


             reply	other threads:[~2024-08-09  9:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09  9:34 Yanfei Xu [this message]
2024-08-09  9:34 ` [v2 1/4] cxl/pci: Fix to record only non-zero ranges Yanfei Xu
2024-08-09 18:55   ` Dan Williams
2024-08-10  8:10     ` Yanfei Xu
2024-08-09  9:34 ` [v2 2/4] cxl/pci: Don't set up decoders for disallowed DVSEC ranges Yanfei Xu
2024-08-09 19:02   ` Dan Williams
2024-08-10 11:36     ` Yanfei Xu
2024-08-09  9:34 ` [v2 3/4] cxl/pci: Check Mem_info_valid bit for each applicable DVSEC range Yanfei Xu
2024-08-09 19:13   ` Dan Williams
2024-08-10 11:50     ` Yanfei Xu
2024-08-09  9:34 ` [v2 4/4] cxl/pci: Simplify the code logic of cxl_hdm_decode_init Yanfei Xu
2024-08-09 19:15   ` Dan Williams
2024-08-10 12:11     ` Yanfei Xu

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=20240809093442.646545-1-yanfei.xu@intel.com \
    --to=yanfei.xu@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=ira.weiny@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=ming4.li@intel.com \
    --cc=vishal.l.verma@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