From: "Randhawa, Jagmeet" <jagmeet.randhawa@intel.com>
To: Gustavo Sousa <gustavo.sousa@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t] tools/dpcd_reg: Advertise the dump command in usage text
Date: Thu, 15 Aug 2024 12:25:17 -0700 [thread overview]
Message-ID: <5a0d233a-bbec-495c-af5e-18a04bc0a282@intel.com> (raw)
In-Reply-To: <20240815191626.49244-1-gustavo.sousa@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]
On 8/15/2024 12:16 PM, Gustavo Sousa wrote:
> When no command is passed, the default operation for dpcd_reg is to dump
> DPCD data. However, passing "dump" explicitly is also supported.
>
> Improve the help message to let the user know about the "dump" command
> and that it is the default operation.
>
> Signed-off-by: Gustavo Sousa<gustavo.sousa@intel.com>
> ---
> tools/dpcd_reg.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/dpcd_reg.c b/tools/dpcd_reg.c
> index 2761168d0030..7d497e36a46b 100644
> --- a/tools/dpcd_reg.c
> +++ b/tools/dpcd_reg.c
> @@ -89,6 +89,7 @@ static void print_usage(void)
> {
> printf("Usage: dpcd_reg [OPTION ...] COMMAND\n\n");
> printf("COMMAND is one of:\n");
> + printf(" dump: Dump dpcd data (default command)\n");
> printf(" read: Read [count] bytes dpcd reg at an offset\n");
> printf(" write: Write a dpcd reg at an offset\n\n");
> printf("Options for the above COMMANDS are\n");
Reviewed-by: Jagmeet Randhawa <jagmeet.randhawa@intel.com>
[-- Attachment #2: Type: text/html, Size: 1708 bytes --]
next prev parent reply other threads:[~2024-08-15 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 19:16 [PATCH i-g-t] tools/dpcd_reg: Advertise the dump command in usage text Gustavo Sousa
2024-08-15 19:25 ` Randhawa, Jagmeet [this message]
2024-08-15 19:47 ` ✓ CI.xeBAT: success for " Patchwork
2024-08-15 19:54 ` ✓ Fi.CI.BAT: " Patchwork
2024-08-15 23:23 ` ✗ CI.xeFULL: failure " Patchwork
2024-08-19 17:42 ` Kamil Konieczny
2024-08-16 10:27 ` ✗ Fi.CI.IGT: " Patchwork
2024-08-19 17:46 ` Kamil Konieczny
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=5a0d233a-bbec-495c-af5e-18a04bc0a282@intel.com \
--to=jagmeet.randhawa@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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