From: "Dilger, Andreas" <andreas.dilger@intel.com>
To: Tabrez khan <khan.tabrez21@gmail.com>
Cc: "jsimmons@infradead.org" <jsimmons@infradead.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"lustre-devel@lists.lustre.org" <lustre-devel@lists.lustre.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging : osc : coding style fix
Date: Wed, 14 Dec 2016 21:27:49 +0000 [thread overview]
Message-ID: <96EAFB90-2162-4155-950D-F586EE1DAF87@intel.com> (raw)
In-Reply-To: <1481749884-25674-1-git-send-email-khan.tabrez21@gmail.com>
On Dec 14, 2016, at 14:11, Tabrez khan <khan.tabrez21@gmail.com> wrote:
>
> Subject: [PATCH] staging : osc : coding style fix
Thanks for sumbitting your patch.
As a general rule, the patch summary line should try to describe
(as best as possible in a single line) what the patch is actually
fixing. It is true this is a "coding style fix" but there are
many possible style fixes and it is better to be as specific as
space allows. Something like:
staging/lustre/osc: remove unnecessary braces
or
staging/lustre/osc: remove braces from single-line body
or
staging/lustre/osc: remove braces in osc_release_write_grant()
would be more specific. This is doubly important if you are
making a large number of similar patches, since it is desirable
to have a (relatively) unique summary line for each patch to
avoid confusion.
> Remove unnecessary braces {} for single if statement block.
> This warning is found using checkpatch.pl.
The commit body is good.
Please resubmit with a new summary line, then you can include:
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Cheers, Andreas
> Signed-off-by: Tabrez khan <khan.tabrez21@gmail.com>
> ---
> drivers/staging/lustre/lustre/osc/osc_cache.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/staging/lustre/lustre/osc/osc_cache.c b/drivers/staging/lustre/lustre/osc/osc_cache.c
> index 4bbe219..5ded31a 100644
> --- a/drivers/staging/lustre/lustre/osc/osc_cache.c
> +++ b/drivers/staging/lustre/lustre/osc/osc_cache.c
> @@ -1420,10 +1420,8 @@ static void osc_release_write_grant(struct client_obd *cli,
> struct brw_page *pga)
> {
> assert_spin_locked(&cli->cl_loi_list_lock);
> - if (!(pga->flag & OBD_BRW_FROM_GRANT)) {
> + if (!(pga->flag & OBD_BRW_FROM_GRANT))
> return;
> - }
> -
> pga->flag &= ~OBD_BRW_FROM_GRANT;
> atomic_long_dec(&obd_dirty_pages);
> cli->cl_dirty_pages--;
> --
> 2.7.4
>
prev parent reply other threads:[~2016-12-14 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 21:11 Tabrez khan
2016-12-14 21:27 ` Dilger, Andreas [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=96EAFB90-2162-4155-950D-F586EE1DAF87@intel.com \
--to=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jsimmons@infradead.org \
--cc=khan.tabrez21@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.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
Powered by JetHome