public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sohny Thomas <sohnythomas@zoho.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: benjamin.romer@unisys.com, david.kershner@unisys.com,
	bryan.thompson@unisys.com, erik.arfvidson@unisys.com,
	devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
	sparmaintainer@unisys.com, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: unisys: virtpci: fixed a brace coding style issue
Date: Wed, 1 Jul 2015 13:06:48 +0530	[thread overview]
Message-ID: <55939890.6090903@zoho.com> (raw)
In-Reply-To: <20150701065749.GA2411@sudip-PC>

Thanks for review, my answers inline

On 01-07-2015 12:27, Sudip Mukherjee wrote:
> On Wed, Jul 01, 2015 at 03:05:45AM +0530, Sohny Thomas wrote:
>>
>> FIX 2 unnecessary braces found by checkpatch.pl
>>
>> Signed-off-by: Sohny Thomas <sohnythomas@zoho.com>
>> ---
>>   drivers/staging/unisys/virtpci/virtpci.c | 11 ++++++-----
>>   1 file changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/staging/unisys/virtpci/virtpci.c b/drivers/staging/unisys/virtpci/virtpci.c
>> index d5ad017..f3674de 100644
>> --- a/drivers/staging/unisys/virtpci/virtpci.c
>> +++ b/drivers/staging/unisys/virtpci/virtpci.c
>> @@ -190,9 +190,10 @@ static int write_vbus_chp_info(struct spar_vbus_channel_protocol *chan,
>>   		return -1;
>>
>>   	off = sizeof(struct channel_header) + chan->hdr_info.chp_info_offset;
>> -	if (chan->hdr_info.chp_info_offset == 0) {
>> +
>> +	if (chan->hdr_info.chp_info_offset == 0)
>>   		return -1;
>> -	}
>> +
> why you are inserting new line here?
I did it so that its readable, will remove it if not required
>
>>   	memcpy(((u8 *)(chan)) + off, info, sizeof(*info));
>>   	return 0;
>>   }
>> @@ -484,10 +485,10 @@ static int delete_vhba(struct del_virt_guestpart *delparams)
>>
>>   	i = virtpci_device_del(NULL /*no parent bus */, VIRTHBA_TYPE,
>>   			       &scsi.wwnn, NULL);
>> -	if (i) {
>> +	if (i)
>>   		return 1;
>> -	}
>> -	return 0;
>> +	else
>> +		return 0;
> No, now this will introduce a new checkpatch warning that "else is not
> required after return". why did you introduce this "else"?
I did this so that the code is more readable and understandable, I 
checked and checkpatch didn't call this out , so its clean.

Otherwise the above code looks like this

if(i)
    return 1;
return 0;

>
> regards
> sudip
>

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



  reply	other threads:[~2015-07-01  7:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 21:35 [PATCH] Staging: unisys: virtpci: fixed a brace coding style issue Sohny Thomas
2015-07-01  6:57 ` Sudip Mukherjee
2015-07-01  7:36   ` Sohny Thomas [this message]
2015-07-01  8:01     ` Julia Lawall
2015-07-01  9:20       ` Sohny Thomas
2015-07-01  9:35         ` Julia Lawall
2015-07-01  8:02     ` Sudip Mukherjee
2015-07-01  8:34       ` Sohny Thomas
2015-07-01  9:15         ` Sudip Mukherjee

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=55939890.6090903@zoho.com \
    --to=sohnythomas@zoho.com \
    --cc=benjamin.romer@unisys.com \
    --cc=bryan.thompson@unisys.com \
    --cc=david.kershner@unisys.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=erik.arfvidson@unisys.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparmaintainer@unisys.com \
    --cc=sudipm.mukherjee@gmail.com \
    /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