From: Joe Perches <joe@perches.com>
To: Jordan Borgner <mail@jordan-borgner.de>,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
x86@kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com
Subject: Re: [PATCH] arch/x86/boot/memory.c: Touched up coding-style issues
Date: Sat, 27 Oct 2018 15:55:19 -0700 [thread overview]
Message-ID: <989035104a2af28816a3c1b9aeb40d54ee88644a.camel@perches.com> (raw)
In-Reply-To: <20181027223231.pyigrae7mhl2xil2@JordanDesktop>
On Sat, 2018-10-27 at 23:32 +0100, Jordan Borgner wrote:
> Added missing parentheses to sizeof() function in detect_memory_e820().
>
> Removed unnecessary braces in detect_memory_e801().
>
> Replaced three if-statements with a ternary if-statement and
> removed an unnecessary integer variable in detect_memory().
>
> This is my first patch I hope it is okay.
Hello Jordan.
While the first bit is generally OK, given some individual
maintainer preferences, it may not also be applied.
Whitespace only changes without logical fixes/upgrades are
generally discouraged outside of drivers/staging.
This bit below though changes behavior.
> @@ -121,16 +120,7 @@ static int detect_memory_88(void)
>
> int detect_memory(void)
> {
> - int err = -1;
> -
> - if (detect_memory_e820() > 0)
> - err = 0;
> -
> - if (!detect_memory_e801())
> - err = 0;
> -
> - if (!detect_memory_88())
> - err = 0;
> -
> - return err;
> + return (detect_memory_e820() > 0 ||
> + !detect_memory_e801() ||
> + !detect_memory_88()) ? 0 : -1;
> }
For instance:
If the first detect_memory_e820 > 0 is true,
the other detect_memory_<e801|88> calls will
not be done.
The original will always perform all three tests.
Regardless, please try to make your first patches
to the linux kernel somewhere in drivers/staging
so get comfortable with the general mechanisms and
styles of kernel patching.
next prev parent reply other threads:[~2018-10-27 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 22:32 Jordan Borgner
2018-10-27 22:55 ` Joe Perches [this message]
2018-10-28 10:46 ` Ingo Molnar
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=989035104a2af28816a3c1b9aeb40d54ee88644a.camel@perches.com \
--to=joe@perches.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@jordan-borgner.de \
--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
all inboxes | Powered by JetHome®