All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Alejandro Colomar <alx.manpages@gmail.com>,
	Benjamin LaHaise <bcrl@kvack.org>,
	Andreas Dilger <adilger@dilger.ca>, Joe Perches <joe@perches.com>
Cc: Alejandro Colomar <colomar.6.4.3@gmail.com>,
	linux-aio@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] fs/aio.c: Cosmetic
Date: Fri, 20 Nov 2020 17:22:45 -0800	[thread overview]
Message-ID: <cdcef7ab-3f06-1d61-35d5-dc9dd2561b8c@infradead.org> (raw)
In-Reply-To: <20201120220647.8026-1-colomar.6.4.3@gmail.com>

On 11/20/20 2:06 PM, Alejandro Colomar wrote:
> Changes:
> - Consistently use 'unsigned int', instead of 'unsigned'.
> - Add a blank line after variable declarations.
> - Move variable declarations to the top of functions.
> - Invert logic of 'if's to reduce indentation and simplify function logic.
> 	- Add goto tags when needed.
> 	- Early return when appropriate.
> - Add braces to 'else' if the corresponding 'if' used braces.
> - Replace spaces by tabs
> - Add spaces when appropriate (after comma, around operators, ...).
> - Split multiple assignments.
> - Align function arguments.
> - Fix typos in comments.
> - s/%Lx/%llx/  Standard C uses 'll'.
> - Remove trailing whitespace in comments.
> 
> This patch does not introduce any actual changes in behavior.
> 
> Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
> ---
> 
> Hi,
> 
> I rebased the patch on top of the current master,
> to update it after recent changes to aio.c.
> 
> Thanks,
> 
> Alex
> 
>  fs/aio.c | 466 +++++++++++++++++++++++++++++--------------------------
>  1 file changed, 243 insertions(+), 223 deletions(-)

Hi,
I reviewed this patch.
I think it looks OK, but I wish that there was a better way to review it.

I'm not asking you to redo the patch, but I think that it would have been easier
to review 2 patches: one that contains trivial changes[1] and one that requires
thinking to review it -- where the trivial changes are not getting in the way
of looking at the non-trivial changes.

[1] the trivial set of changes, taken from your patch description:

> - Consistently use 'unsigned int', instead of 'unsigned'.
> - Add a blank line after variable declarations.
> - Move variable declarations to the top of functions.
> - Add braces to 'else' if the corresponding 'if' used braces.
> - Replace spaces by tabs
> - Add spaces when appropriate (after comma, around operators, ...).
> - Split multiple assignments.
> - Align function arguments.
> - Fix typos in comments.
> - s/%Lx/%llx/  Standard C uses 'll'.
> - Remove trailing whitespace in comments.

OK, that's everything except for this:
> - Invert logic of 'if's to reduce indentation and simplify function logic.
> 	- Add goto tags when needed.
> 	- Early return when appropriate.


thanks.
-- 
~Randy
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>


  reply	other threads:[~2020-11-21  1:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 15:05 [PATCH] fs/aio.c: Cosmetic Alejandro Colomar
2020-11-02 15:24 ` Alejandro Colomar
2020-11-02 21:58   ` [PATCH v2] " Alejandro Colomar
2020-11-03  0:50     ` Andreas Dilger
2020-11-03  3:22       ` Joe Perches
2020-11-03  9:50         ` [PATCH v3] " Alejandro Colomar
2020-11-20 22:06           ` [PATCH v4] " Alejandro Colomar
2020-11-21  1:22             ` Randy Dunlap [this message]
2020-11-21 11:41               ` Alejandro Colomar

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=cdcef7ab-3f06-1d61-35d5-dc9dd2561b8c@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=adilger@dilger.ca \
    --cc=alx.manpages@gmail.com \
    --cc=bcrl@kvack.org \
    --cc=colomar.6.4.3@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-aio@kvack.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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 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.