From: Yanfei Xu <yanfei.xu@intel.com>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: <linux-cxl@vger.kernel.org>, <dave@stgolabs.net>,
<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>
Subject: Re: [v3 0/4] Fixes for hdm docoder initialization from DVSEC ranges
Date: Wed, 28 Aug 2024 10:45:19 +0800 [thread overview]
Message-ID: <30e8c934-1017-4e0b-9cb1-e8913b212ba4@intel.com> (raw)
In-Reply-To: <20240827170813.00004d7c@Huawei.com>
On 8/28/2024 12:08 AM, Jonathan Cameron wrote:
> On Tue, 13 Aug 2024 19:05:28 +0800
> Yanfei Xu <yanfei.xu@intel.com> wrote:
>
>> The first and third patch are intended to fix potential issues regarding to
>> retrieve and record DVSEC ranges. The second and fourth are cleanup.
>
> typo in patch title. decoder
>
>
> Also, good to include cxl: as prefix to the patch title.
>
Got it, will do.
>>
>> v2->v3:
>> - improved the commit message of patch1 to indicate potential impact of
>> the change. (Dan)
>> - Dropped un-appropriate "Fixes" tag. (Dan)
>> - Dropped the patch2 which is a code movement in original patchset.
>> - Separated the original patch3 into cleanup one and logic change one which
>> are corresponding to patch2 and patch3 in current patchset. (Dan)
>>
>> v2:https://lore.kernel.org/linux-cxl/20240809093442.646545-1-yanfei.xu@intel.com/T/#t
>>
>> Yanfei Xu (4):
>> cxl/pci: Fix to record only non-zero ranges
>> cxl/pci: Remove duplicated implementation of waiting for
>> memory_info_valid
>> cxl/pci: Check Mem_info_valid bit for each applicable DVSEC
>> cxl/pci: simplify the check of mem_enabled in cxl_hdm_decode_init()
>>
>> drivers/cxl/core/pci.c | 74 +++++++++--------------------------
>> drivers/cxl/cxl.h | 2 +-
>> drivers/cxl/port.c | 2 +-
>> tools/testing/cxl/test/mock.c | 4 +-
>> 4 files changed, 23 insertions(+), 59 deletions(-)
>>
>
>
prev parent reply other threads:[~2024-08-28 2:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 11:05 [v3 0/4] Fixes for hdm docoder initialization from DVSEC ranges Yanfei Xu
2024-08-13 11:05 ` [v3 1/4] cxl/pci: Fix to record only non-zero ranges Yanfei Xu
2024-08-27 16:11 ` Jonathan Cameron
2024-08-13 11:05 ` [v3 2/4] cxl/pci: Remove duplicated implementation of waiting for memory_info_valid Yanfei Xu
2024-08-27 16:16 ` Jonathan Cameron
2024-08-28 2:49 ` Yanfei Xu
2024-08-13 11:05 ` [v3 3/4] cxl/pci: Check Mem_info_valid bit for each applicable DVSEC Yanfei Xu
2024-08-27 16:22 ` Jonathan Cameron
2024-08-28 2:54 ` Yanfei Xu
2024-08-13 11:05 ` [v3 4/4] cxl/pci: simplify the check of mem_enabled in cxl_hdm_decode_init() Yanfei Xu
2024-08-27 16:25 ` Jonathan Cameron
2024-08-27 5:04 ` [v3 0/4] Fixes for hdm docoder initialization from DVSEC ranges Yanfei Xu
2024-08-27 16:08 ` Jonathan Cameron
2024-08-28 2:45 ` Yanfei Xu [this message]
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=30e8c934-1017-4e0b-9cb1-e8913b212ba4@intel.com \
--to=yanfei.xu@intel.com \
--cc=Jonathan.Cameron@Huawei.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=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