From: Christoph Hellwig <hch@infradead.org>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Doug Anderson <dianders@chromium.org>
Subject: Re: [PATCH] btrfs: Remove extra parentheses from condition in copy_items()
Date: Thu, 27 Jul 2017 03:09:45 -0700 [thread overview]
Message-ID: <20170727100945.GA5221@infradead.org> (raw)
In-Reply-To: <20170726204759.160649-1-mka@chromium.org>
> - if ((i == (nr - 1)))
> + if (i == (nr - 1))
Please remove the other set of redundant parentheses as well if you
change that line.
prev parent reply other threads:[~2017-07-27 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 20:47 [PATCH] btrfs: Remove extra parentheses from condition in copy_items() Matthias Kaehlcke
2017-07-27 10:09 ` Christoph Hellwig [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=20170727100945.GA5221@infradead.org \
--to=hch@infradead.org \
--cc=clm@fb.com \
--cc=dianders@chromium.org \
--cc=dsterba@suse.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.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;
as well as URLs for NNTP newsgroup(s).