From: Jan Beulich <jbeulich@suse.com>
To: Fouad Hilly <fouad.hilly@cloud.com>
Cc: Anthony PERARD <anthony.perard@vates.tech>,
Juergen Gross <jgross@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v5 3/4] x86/ucode: Introduce --force option to xen-ucode
Date: Fri, 12 Jul 2024 15:27:38 +0200 [thread overview]
Message-ID: <c4157096-cfc6-4455-a5f4-c2af94591284@suse.com> (raw)
In-Reply-To: <20240712130749.1272741-4-fouad.hilly@cloud.com>
On 12.07.2024 15:07, Fouad Hilly wrote:
> @@ -79,6 +81,8 @@ static void usage(FILE *stream, const char *name)
> "options:\n"
> " -h, --help display this help\n"
> " -s, --show-cpu-info show CPU information\n"
> + " -f, --force skip certain checks; do not use unless you"
> + "know exactly what you are doing\n"
Would this output line perhaps better be wrapped explicitly, to avoid
odd wrapping effects on terminals not wider than 80 chars? In any event
there's a blank missing at the present source wrapping point.
Jan
next prev parent reply other threads:[~2024-07-12 13:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 13:07 [PATCH v5 0/4] x86/xen-ucode: Introduce --force option Fouad Hilly
2024-07-12 13:07 ` [PATCH v5 1/4] x86/ucode: Introduce XENPF_microcode_update2 with flags parameter Fouad Hilly
2024-07-12 13:07 ` [PATCH v5 2/4] x86/ucode: refactor xen-ucode to utilize getopt Fouad Hilly
2024-07-16 14:51 ` Jan Beulich
2024-07-23 9:41 ` Fouad Hilly
2024-07-24 16:55 ` Anthony PERARD
2024-08-19 8:56 ` Fouad Hilly
2024-07-12 13:07 ` [PATCH v5 3/4] x86/ucode: Introduce --force option to xen-ucode Fouad Hilly
2024-07-12 13:27 ` Jan Beulich [this message]
2024-07-23 9:39 ` Fouad Hilly
2024-07-12 13:07 ` [PATCH v5 4/4] x86/ucode: Utilize ucode_force and remove opt_ucode_allow_same Fouad Hilly
2024-07-16 14:59 ` Jan Beulich
2024-07-23 9:52 ` 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=c4157096-cfc6-4455-a5f4-c2af94591284@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=fouad.hilly@cloud.com \
--cc=jgross@suse.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.