From: Jan Beulich <jbeulich@suse.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 1/3] xen/cmdline: fix printf format specifier in no_config_param()
Date: Mon, 26 Feb 2024 09:29:02 +0100 [thread overview]
Message-ID: <3ed4e0e9-fec4-4e8b-a52d-fb4756ae50cd@suse.com> (raw)
In-Reply-To: <20240223120616.73503-2-roger.pau@citrix.com>
On 23.02.2024 13:06, Roger Pau Monne wrote:
> '*' sets the width field, which is the minimum number of characters to output,
> but what we want in no_config_param() is the precision instead, which is '.*'
> as it imposes a maximum limit on the output.
>
> Fixes: 68d757df8dd2 ('x86/pv: Options to disable and/or compile out 32bit PV support')
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
next prev parent reply other threads:[~2024-02-26 8:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 12:06 [PATCH v2 0/3] x86/spec: improve command line parsing Roger Pau Monne
2024-02-23 12:06 ` [PATCH v2 1/3] xen/cmdline: fix printf format specifier in no_config_param() Roger Pau Monne
2024-02-26 8:29 ` Jan Beulich [this message]
2024-02-23 12:06 ` [PATCH v2 2/3] x86/spec: fix BRANCH_HARDEN option to only be set when build-enabled Roger Pau Monne
2024-02-26 8:33 ` Jan Beulich
2024-02-26 8:42 ` Jan Beulich
2024-02-26 9:09 ` Roger Pau Monné
2024-02-26 9:33 ` Jan Beulich
2024-02-26 9:57 ` Roger Pau Monné
2024-02-26 10:16 ` Jan Beulich
2024-02-23 12:06 ` [PATCH v2 3/3] x86/spec: fix INDIRECT_THUNK " Roger Pau Monne
2024-02-26 8:40 ` Jan Beulich
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=3ed4e0e9-fec4-4e8b-a52d-fb4756ae50cd@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=julien@xen.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--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.