From: Jan Beulich <jbeulich@suse.com>
To: Fouad Hilly <fouad.hilly@cloud.com>
Cc: Anthony PERARD <anthony.perard@vates.tech>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v6 2/4] x86/ucode: refactor xen-ucode to utilize getopt
Date: Thu, 25 Jul 2024 10:37:34 +0200 [thread overview]
Message-ID: <772e656a-8d03-47b3-884e-4aeeb48b1c0d@suse.com> (raw)
In-Reply-To: <20240725082725.2685481-3-fouad.hilly@cloud.com>
On 25.07.2024 10:27, Fouad Hilly wrote:
> @@ -71,12 +72,29 @@ static void show_curr_cpu(FILE *f)
> }
> }
>
> +static void usage(FILE *stream, const char *name)
> +{
> + fprintf(stream,
> + "%s: Xen microcode updating tool\n"
> + "options:\n"
> + " -h, --help display this help\n"
> + " -s, --show-cpu-info show CPU information\n"
> + "Usage: %s [microcode file | options]\n", name, name);
You did see Anthony's comments on this before sending the new version,
didn't you? I agree with him (and I'm somewhat embarrassed that I didn't
notice this myself earlier on).
> @@ -146,4 +176,10 @@ int main(int argc, char *argv[])
> close(fd);
>
> return 0;
> +
> + ext_err:
> + fprintf(stderr,
> + "%s: unable to process command line arguments\n", argv[0]);
> + usage(stderr, argv[0]);
> + exit(EXIT_FAILURE);
> }
And there was a comment on this, too.
Jan
next prev parent reply other threads:[~2024-07-25 8:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 8:27 [PATCH v6 0/4] x86/xen-ucode: Introduce --force option Fouad Hilly
2024-07-25 8:27 ` [PATCH v6 1/4] x86/ucode: Introduce XENPF_microcode_update2 with flags parameter Fouad Hilly
2024-07-25 8:27 ` [PATCH v6 2/4] x86/ucode: refactor xen-ucode to utilize getopt Fouad Hilly
2024-07-25 8:37 ` Jan Beulich [this message]
2024-07-25 8:41 ` Jan Beulich
2024-08-19 8:56 ` Fouad Hilly
2024-07-25 8:27 ` [PATCH v6 3/4] x86/ucode: Introduce --force option to xen-ucode Fouad Hilly
2024-07-25 8:44 ` Jan Beulich
2024-08-19 8:56 ` Fouad Hilly
2024-08-19 9:47 ` Anthony PERARD
2024-08-22 7:22 ` Fouad Hilly
2024-07-25 8:27 ` [PATCH v6 4/4] x86/ucode: Utilize ucode_force and remove opt_ucode_allow_same Fouad Hilly
2024-07-29 11:30 ` Jan Beulich
2024-08-19 8:57 ` Fouad Hilly
2024-08-19 9:22 ` Jan Beulich
2024-08-22 7:22 ` Fouad Hilly
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=772e656a-8d03-47b3-884e-4aeeb48b1c0d@suse.com \
--to=jbeulich@suse.com \
--cc=anthony.perard@vates.tech \
--cc=fouad.hilly@cloud.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.