From: "Colin King (gmail)" <colin.i.king@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Darren Hart <dvhart@infradead.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Shuah Khan <shuah@kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: selftests/futex: issue with -g option help text
Date: Fri, 8 Aug 2025 12:01:49 +0100 [thread overview]
Message-ID: <358d6fae-80be-469c-a8d9-c4e786781a65@gmail.com> (raw)
In-Reply-To: <20250808105435.PYwBvZ-6@linutronix.de>
[-- Attachment #1.1.1: Type: text/plain, Size: 880 bytes --]
Hi,
On 08/08/2025 11:54, Sebastian Andrzej Siewior wrote:
> On 2025-08-08 11:40:23 [+0100], Colin King (gmail) wrote:
>> Hi,
> Hi,
>
>> Namely:
>>
>> static void usage(char *prog)
>> {
>> printf("Usage: %s\n", prog);
>> printf(" -c Use color\n");
>> printf(" -g Test global hash instead intead local immutable
>> \n");
>> printf(" -h Display this help message\n");
>> printf(" -v L Verbosity level: %d=QUIET %d=CRITICAL %d=INFO\n",
>> VQUIET, VCRITICAL, VINFO);
>> }
>>
>>
>> there word "intead" for the -g option should be removed, but I'm also
>> finding the resulting text hard to parse, perhaps it needs to be rephrased?
>
> Test global hash instead instead private hash
Surely:
Test global hash instead of private hash
>
> ?
>
>> Colin
>
> Sebastian
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 4901 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2025-08-08 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 10:40 selftests/futex: issue with -g option help text Colin King (gmail)
2025-08-08 10:54 ` Sebastian Andrzej Siewior
2025-08-08 11:01 ` Colin King (gmail) [this message]
2025-08-08 11:16 ` Sebastian Andrzej Siewior
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=358d6fae-80be-469c-a8d9-c4e786781a65@gmail.com \
--to=colin.i.king@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).