From: Marc Herbert <marc.herbert@linux.intel.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: linux-cxl@vger.kernel.org, nvdimm@lists.linux.dev, dave.jiang@intel.com
Subject: Re: [ndctl PATCH] test/common: document magic number CXL_TEST_QOS_CLASS=42
Date: Fri, 22 Aug 2025 20:07:12 -0700 [thread overview]
Message-ID: <19885c2f-59d8-45d2-9d2a-456d9f4b8304@linux.intel.com> (raw)
In-Reply-To: <aKizZaxYjEJ3g_Rc@aschofie-mobl2.lan>
On 2025-08-22 11:13, Alison Schofield wrote:
> On Fri, Aug 22, 2025 at 02:55:34AM +0000, marc.herbert@linux.intel.com wrote:
>> From: Marc Herbert <marc.herbert@linux.intel.com>
>>
>> This magic number must match kernel code. Make that corresponding kernel
>> code much less time-consuming to find.
>
> The 'must match' is the important part. Include that in the comment.
Good point, will do!
> Why expect the user to parse a git describe string and go fishing.
> Just tell them it is defined in the cxl-test module.
>
git knows how to parse back the git describe string; readers don't need
to parse anything. As explained in the commit message, it's convenient
because it holds in a single string both the immutable commit ID _and_
an indication of the minimum kernel version required.
Why tell users to "go fishing" for the cxl-test module when they can
find the location directly with a single git command. This is real: I
actually wasted a fair amount of time searching for that constant in
drivers/cxl/ because I assumed the cxl-test driver was there. This
comment is not meant for experts; if they needed it then it would not
have been missing for so long.
Last but not least, code and files move around and get renamed. This
commit will never change, so it provides an immutable starting point in
case things change.
I'll add both, it should still fit on one line.
next prev parent reply other threads:[~2025-08-23 3:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 2:55 [ndctl PATCH] test/common: document magic number CXL_TEST_QOS_CLASS=42 marc.herbert
2025-08-22 15:57 ` Dave Jiang
2025-08-22 18:13 ` Alison Schofield
2025-08-23 3:07 ` Marc Herbert [this message]
2025-08-25 1:36 ` Alison Schofield
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=19885c2f-59d8-45d2-9d2a-456d9f4b8304@linux.intel.com \
--to=marc.herbert@linux.intel.com \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
/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