From: Steven Rostedt <rostedt@goodmis.org>
To: B K Karthik <bkkarthik@pesu.pes.edu>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Arvind Sankar <nivedita@alum.mit.edu>,
"glider@google.com" <glider@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] init: main.c: Fixed a brace coding style issue.
Date: Sun, 28 Jun 2020 15:05:07 -0400 [thread overview]
Message-ID: <20200628150507.5f5181fe@oasis.local.home> (raw)
In-Reply-To: <20200628134100.mseebxf3dot56eia@pesu-pes-edu>
On Sun, 28 Jun 2020 09:41:00 -0400
B K Karthik <bkkarthik@pesu.pes.edu> wrote:
> Fixed a coding style issue.
>
> Signed-off-by: B K Karthik <karthik.bk2000@live.com>
> ---
> init/main.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/init/main.c b/init/main.c
> index 9127b240fd26..d8477fb95bec 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -385,11 +385,11 @@ static u32 boot_config_checksum(unsigned char *p, u32 size)
> static int __init bootconfig_params(char *param, char *val,
> const char *unused, void *arg)
> {
> - if (strcmp(param, "bootconfig") == 0) {
> + if (strcmp(param, "bootconfig") == 0)
> bootconfig_found = true;
> - } else if (strcmp(param, "--") == 0) {
> + else if (strcmp(param, "--") == 0)
> initargs_found = true;
> - }
> +
NAK.
perhaps for simple if () ;else ; statements I'd be OK with this change,
but this is a if () ; else if () ; which is up to the preference of the
user. I find the brackets making it easier to see that this is not a
normal if () ; else ;
-- Steve
> return 0;
> }
>
> --
> 2.20.1
>
prev parent reply other threads:[~2020-06-28 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 13:41 B K Karthik
2020-06-28 19:05 ` Steven Rostedt [this message]
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=20200628150507.5f5181fe@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=bkkarthik@pesu.pes.edu \
--cc=glider@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mhiramat@kernel.org \
--cc=nivedita@alum.mit.edu \
/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®