From: Rebecca Mckeever <remckee0@gmail.com>
To: shaoqin.huang@intel.com
Cc: rppt@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] memblock test: Modify the obsolete description in README
Date: Wed, 27 Jul 2022 23:05:01 -0500 [thread overview]
Message-ID: <YuIK7cU8uH7zVP+S@bertie> (raw)
In-Reply-To: <20220728011228.23691-1-shaoqin.huang@intel.com>
On Wed, Jul 27, 2022 at 07:12:28PM -0600, shaoqin.huang@intel.com wrote:
> From: Shaoqin Huang <shaoqin.huang@intel.com>
>
> The VERBOSE option in Makefile has been moved, but there still have the
> description left in README. For now, we use `-v` options when running
> memblock test to print information, so using the new to replace the
> obsolete items.
>
Thanks for catching this!
> Signed-off-by: Shaoqin Huang <shaoqin.huang@intel.com>
> ---
> Changelog:
> ----------
> v2:
> - Tweak the sentence to make it more clear and continuesly.
> - Commit log changes.
>
> tools/testing/memblock/README | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/tools/testing/memblock/README b/tools/testing/memblock/README
> index 058146b528a5..d3875e7065fd 100644
> --- a/tools/testing/memblock/README
> +++ b/tools/testing/memblock/README
> @@ -33,16 +33,19 @@ To run the tests, build the main target and run it:
>
> $ make && ./main
>
> -A successful run produces no output. It is also possible to override different
> -configuration parameters. For example, to include verbose output, specify the
> -VERBOSE flag when building the main target:
> +A successful run produces no output. It is possible to control the behavior
> +by passing options from command line. For example, to include verbose output,
> +append the `-v` options when you run the tests:
>
> -$ make VERBOSE=1
> +$ ./main -v
>
> This will print information about which functions are being tested and the
> number of test cases that passed.
>
> -To simulate enabled NUMA, use:
> +For the full list of options from command line, see `./main --help`.
--help will display the list of command line options by default, but a
help command line option isn't explicitly implemented. I'm planning to add
the help option, so if you want to remove this sentence, I will add it when
I implement the help option.
> +
> +It is also possible to override different configuration parameters to change it
> +test functions. For example, To simulate enabled NUMA, use:
>
> $ make NUMA=1
>
Maybe you could add "build" before "options" in the line after this:
-For the full list of options, see `make help`.
+For the full list of build options, see `make help`.
> --
> 2.30.2
>
>
next prev parent reply other threads:[~2022-07-28 4:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 1:12 shaoqin.huang
2022-07-28 4:05 ` Rebecca Mckeever [this message]
2022-07-28 5:08 ` Huang, Shaoqin
2022-07-28 9:01 ` Mike Rapoport
2022-07-28 9:14 ` Huang, Shaoqin
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=YuIK7cU8uH7zVP+S@bertie \
--to=remckee0@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--cc=shaoqin.huang@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