From: "rs@mage.me.uk" <rs@mage.me.uk>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, speakup@braille.uwo.ca,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: speakup: buffers: Fixed a return value coding style issue.
Date: Thu, 27 Feb 2014 18:12:48 +0000 [thread overview]
Message-ID: <530F8020.3040000@mage.me.uk> (raw)
In-Reply-To: <20140227164051.GA25183@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
When checking buffers.c with checkpatch.pl it throws the following
error: drivers/staging/speakup/buffers.c:58: ERROR: return is not a
function, parentheses are not required
I watched one of your talks, it's very informative and concise:
http://www.youtube.com/watch?v=LLBrBBImJt4&feature=youtu.be
Thanks,
Reza Snowdon
On 27/02/14 16:40, Greg KH wrote:
> On Thu, Feb 27, 2014 at 04:26:42PM +0000, Reza Snowdon wrote:
>> Fixed a coding style issue.
>>
>> Signed-off-by: Reza Snowdon <rs@mage.me.uk>
>> ---
>> drivers/staging/speakup/buffers.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/staging/speakup/buffers.c b/drivers/staging/speakup/buffers.c
>> index 382973e..8d7caa7 100644
>> --- a/drivers/staging/speakup/buffers.c
>> +++ b/drivers/staging/speakup/buffers.c
>> @@ -55,7 +55,8 @@ static int synth_buffer_free(void)
>>
>> int synth_buffer_empty(void)
>> {
>> - return (buff_in == buff_out);
>> + int buff_comparison = (buff_in == buff_out);
>> + return buff_comparison;
>
> What's wrong with the original code here? If anything, just drop the
> (), but really, it's fine, leave it alone, it's obvious what is
> happening is ok.
>
> thanks,
>
> greg k-h
>
--
Regards,
Reza Snowdon
[-- Attachment #2: 0001-Staging-speakup-buffers-Fixed-a-return-coding-style-.patch --]
[-- Type: text/x-patch, Size: 980 bytes --]
>From a2dda399463c20f63306e31b743e0c9c3be2ca3a Mon Sep 17 00:00:00 2001
From: Reza Snowdon <rs@mage.me.uk>
Date: Thu, 27 Feb 2014 17:57:59 +0000
Subject: [PATCH] Staging: speakup: buffers: Fixed a return coding style issue
When checking buffers.c with checkpatch.pl it throws the following error: drivers/staging/speakup/buffers.c:58: ERROR: return is not a function, parentheses are not required
Fixed error by removing parenthesis.
Signed-off-by: Reza Snowdon <rs@mage.me.uk>
---
drivers/staging/speakup/buffers.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/speakup/buffers.c b/drivers/staging/speakup/buffers.c
index 382973e..5e6ec13 100644
--- a/drivers/staging/speakup/buffers.c
+++ b/drivers/staging/speakup/buffers.c
@@ -55,7 +55,7 @@ static int synth_buffer_free(void)
int synth_buffer_empty(void)
{
- return (buff_in == buff_out);
+ return buff_in == buff_out;
}
EXPORT_SYMBOL_GPL(synth_buffer_empty);
--
1.7.10.4
next prev parent reply other threads:[~2014-02-27 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 16:26 [PATCH] Staging: speakup: buffers: Fixed a return value coding style issue Reza Snowdon
2014-02-27 16:40 ` Greg KH
2014-02-27 18:12 ` rs [this message]
2014-02-27 19:10 ` Greg KH
2014-02-27 16:47 ` Dan Carpenter
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=530F8020.3040000@mage.me.uk \
--to=rs@mage.me.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=speakup@braille.uwo.ca \
/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