public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tamir Suliman <tsuliman@linuxvaults.com>
To: Justin Skists <justin.skists@juzza.co.uk>,
	w.d.hubbs@gmail.com, gregkh@linuxfoundation.org,
	speakup@linux-speakup.org
Cc: devel@driverdev.osuosl.org, chris@the-brannons.com,
	dhowells@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] drivers/speakup: Fix style and coding warnings
Date: Wed, 4 Jul 2018 22:46:05 +0300	[thread overview]
Message-ID: <fb7d3816-255d-15e7-b9ef-533b1167f73c@linuxvaults.com> (raw)
In-Reply-To: <1527895743.93688.1530605455516@email.1and1.co.uk>


Interesting construct...  Yeah I'm little bit rusty on my C 
/programming  . I understand  proper coding style may be should end with 
else so I wasn't sure .. however this resolved the warnings. :)


Did you compile this?


Yes I did compile  however the only issue i found when I'm compiling is  
modules symvers missing messages researched online and found couple of 
articles that recommended  to  run full kernel build . Please bear with 
me I'm new to this and very excited about learning and contributing.



On 7/3/2018 11:10 AM, Justin Skists wrote:
>> On 03 July 2018 at 08:31 Tamir Suliman <tsuliman@linuxvaults.com> wrote:
>> +++ b/drivers/staging/speakup/keyhelp.c
>> @@ -167,7 +167,7 @@ int spk_handle_help(struct vc_data *vc, u_char type, u_char ch, u_short key)
>>   		synth_printf("%s\n", spk_msg_get(MSG_HELP_INFO));
>>   		build_key_data(); /* rebuild each time in case new mapping */
>>   		return 1;
>> -	} else {
>> +	} else if {
> Interesting construct...
>
>
>> @@ -787,7 +787,7 @@ static ssize_t message_store_helper(const char *buf, size_t count,
>>   			continue;
>>   		}
>>   
>> -		index = simple_strtoul(cp, &temp, 10);
>> +		index = simple_ktrtoul(cp, &temp, 10);
> Did you compile this?
>
>
> Justin.


  reply	other threads:[~2018-07-04 19:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03  7:31 [PATCH 3/3] drivers/speakup: Fix style and coding warnings Tamir Suliman
2018-07-03  7:40 ` Greg KH
2018-07-03  8:10 ` Justin Skists
2018-07-04 19:46   ` Tamir Suliman [this message]
2018-07-05 11:46     ` Dan Carpenter
2018-07-05 11:55   ` 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=fb7d3816-255d-15e7-b9ef-533b1167f73c@linuxvaults.com \
    --to=tsuliman@linuxvaults.com \
    --cc=chris@the-brannons.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dhowells@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=justin.skists@juzza.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=speakup@linux-speakup.org \
    --cc=w.d.hubbs@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