From: Ingo Molnar <mingo@kernel.org>
To: Joseph Thelen <jthelen@sgi.com>
Cc: linux-kernel@vger.kernel.org, Alex Thorlton <athorlton@sgi.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-efi@vger.kernel.org
Subject: Re: [PATCH] x86/efi: Auto enable EFI memmap on SGI UV systems
Date: Wed, 8 Jun 2016 13:12:23 +0200 [thread overview]
Message-ID: <20160608111223.GA5772@gmail.com> (raw)
In-Reply-To: <1464900635-11957-2-git-send-email-jthelen@sgi.com>
* Joseph Thelen <jthelen@sgi.com> wrote:
> static int __init setup_add_efi_memmap(char *arg)
> {
> + static bool arg_as_bool;
Why hidden inside local variables as static?
> + int ret = strtobool(arg, &arg_as_bool);
> +
> + /* check for a non-existent arg, to maintain backward compatibility */
> + if (!arg) {
> + add_efi_memmap = EFI_MEMMAP_ENABLED;
> + } else {
> + if (ret) {
> + /* a bad argument was passed... */
> + return ret;
> + } else {
> + if (arg_as_bool)
> + add_efi_memmap = EFI_MEMMAP_ENABLED;
> + else
> + add_efi_memmap = EFI_MEMMAP_DISABLED;
> + }
> + }
> +
> return 0;
And that's a really weird code flow!
How about something straightforward:
int val = 0;
int ret;
/* Check for a non-existent arg, to maintain backward compatibility: */
if (!arg) {
add_efi_memmap = EFI_MEMMAP_ENABLED;
return 0;
}
ret = strtobool(arg, &val);
/* Was a bad argument passed? */
if (ret)
return ret;
if (val)
add_efi_memmap = EFI_MEMMAP_ENABLED;
else
add_efi_memmap = EFI_MEMMAP_DISABLED;
return 0;
?
Also note the rename to 'val'.
Thanks,
Ingo
next prev parent reply other threads:[~2016-06-08 11:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 20:50 [RFC PATCH] x86/efi: Auto enable EFI memmap on SGI UV systems Joseph Thelen
2016-06-02 20:50 ` [PATCH] " Joseph Thelen
2016-06-08 11:12 ` Ingo Molnar [this message]
2016-06-14 22:19 ` Joseph Thelen
2016-06-08 12:36 ` Matt Fleming
2016-06-14 22:34 ` Joseph Thelen
2016-06-17 20:57 ` Joseph Thelen
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=20160608111223.GA5772@gmail.com \
--to=mingo@kernel.org \
--cc=athorlton@sgi.com \
--cc=hpa@zytor.com \
--cc=jthelen@sgi.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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