From: David Miller <davem@davemloft.net>
To: geunsik.lim@gmail.com
Cc: isdn@linux-pingi.de, lucas.demarchi@profusion.mobi,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Keep kernel coding style rule of hfs-s+/sp source
Date: Wed, 01 Feb 2012 02:06:02 -0500 (EST) [thread overview]
Message-ID: <20120201.020602.131240058939599710.davem@davemloft.net> (raw)
In-Reply-To: <1328079593-19197-1-git-send-email-geunsik.lim@gmail.com>
From: Geunsik Lim <geunsik.lim@gmail.com>
Date: Wed, 1 Feb 2012 15:59:53 +0900
> Modified for kernel coding style rule of hfs-s+/sp device driver .
> . reference: ./Documentation/CodingStyle
>
> ex)
> 60 Don't put multiple statements on a single line unless you have
> 61 something to hide:
> 62
> 63 if (condition) do_this;
> 64 do_something_everytime;
>
> Signed-off-by: Geunsik Lim <geunsik.lim@samsung.com>
This was probably there to eliminate compiler warnings or avoid the
code being eliminated completely, because the result of the register
read is unused.
Have you verified that neither is the case here?
To be honest I very strongly dislike patches like this. You're
patching a driver that very few people use, and changes like this can
only risk possible regressions that will be hard to notice and it's
not like people scour over this driver often and thus will be upset by
frequently seeing some minor coding style infraction.
I'm not applying this patch.
next prev parent reply other threads:[~2012-02-01 7:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 6:59 Geunsik Lim
2012-02-01 7:06 ` David Miller [this message]
[not found] ` <CAGFP0LKU0uDPQzhCy8qmThXQ9f9ofSnQrbr2dO83i+usc85_FQ@mail.gmail.com>
2012-02-01 7:48 ` David Miller
2012-02-02 19:01 ` Karsten Keil
2012-02-02 19:11 ` Joe Perches
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=20120201.020602.131240058939599710.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=geunsik.lim@gmail.com \
--cc=isdn@linux-pingi.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=netdev@vger.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®