From: Dan Williams <dan.j.williams@intel.com>
To: Alison Schofield <alison.schofield@intel.com>,
Dave Jiang <dave.jiang@intel.com>
Cc: <linux-cxl@vger.kernel.org>, <dan.j.williams@intel.com>,
<Jonathan.Cameron@huawei.com>, <dave@stgolabs.net>,
<vishal.l.verma@intel.com>, <ira.weiny@intel.com>
Subject: Re: [PATCH v3] cxl: Add cxl_num_decoders_committed() usage to cxl_test
Date: Mon, 4 Dec 2023 16:43:06 -0800 [thread overview]
Message-ID: <656e721a3bc4a_45e0129458@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <ZUwFCM61s0864EA6@aschofie-mobl2>
Alison Schofield wrote:
> On Mon, Nov 06, 2023 at 10:26:45AM -0700, Dave Jiang wrote:
> > Commit 458ba8189cb4 ("cxl: Add cxl_decoders_committed() helper") missed the
> > conversion for cxl_test. Add usage of cxl_num_decoders_committed() to
> > replace the open coding.
> >
> > Suggested-by: Alison Schofield <alison.schofield@intel.com>
>
> Search for more usages of commit_end in cxl.c that may use new helper.
Did you have one in mind? Of these:
tools/testing/cxl/test/cxl.c:672: if (port->commit_end + 1 != id) {
tools/testing/cxl/test/cxl.c:675: dev_name(&cxld->dev), port->id, port->commit_end + 1);
tools/testing/cxl/test/cxl.c:679: port->commit_end++;
tools/testing/cxl/test/cxl.c:694: if (port->commit_end != id) {
tools/testing/cxl/test/cxl.c:697: dev_name(&cxld->dev), port->id, port->commit_end);
tools/testing/cxl/test/cxl.c:701: port->commit_end--;
tools/testing/cxl/test/cxl.c:793: port->commit_end = cxld->id;
tools/testing/cxl/test/cxl.c:825: iter->commit_end = 0;
Only tools/testing/cxl/test/cxl.c:694 looks interesting, but given
cxl_decoder_reset() does not use cxl_num_decoders_committed(), neither
should mock_decoder_reset().
prev parent reply other threads:[~2023-12-05 0:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 17:26 [PATCH v3] cxl: Add cxl_num_decoders_committed() usage to cxl_test Dave Jiang
2023-11-06 18:33 ` fan
2023-11-08 22:00 ` Alison Schofield
2023-12-05 0:43 ` Dan Williams [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=656e721a3bc4a_45e0129458@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--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