mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luis de Bethencourt <luis@debethencourt.com>
To: Christian Colic <colic.christian@gmail.com>
Cc: w.d.hubbs@gmail.com, chris@the-brannons.com, kirk@reisers.ca,
	samuel.thibault@ens-lyon.org, gregkh@linuxfoundation.org,
	speakup@linux-speakup.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: speakup: (coding style) Add spaces around operands (checkpatch checks)
Date: Thu, 19 Nov 2015 15:12:03 +0100	[thread overview]
Message-ID: <20151119141203.GA25601@goodgumbo.baconseed.org> (raw)
In-Reply-To: <20151119134059.GA15096@lenovo>

Hi al,

Looks good and silences the checkpatch warnings.

Christian,
There are more checkpatch warnings in this file. Could you fix them as well?


Reviewed-by: Luis de Bethencourt <luisbg@osg.samsung.com>


On Thu, Nov 19, 2015 at 02:40:59PM +0100, Christian Colic wrote:
> Fix checkpatch check: CHECK: spaces preferred around that '-' (ctx:VxV)
> Add spaces around operands to fix these warnings.
> 
> Signed-off-by: Christian Colic <colic.christian@gmail.com>
> ---
>  drivers/staging/speakup/keyhelp.c | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/staging/speakup/keyhelp.c b/drivers/staging/speakup/keyhelp.c
> index 02d5c70..d14089a 100644
> --- a/drivers/staging/speakup/keyhelp.c
> +++ b/drivers/staging/speakup/keyhelp.c
> @@ -74,7 +74,7 @@ static void build_key_data(void)
>  		for (i = 0; i < nstates; i++, kp++) {
>  			if (!*kp)
>  				continue;
> -			if ((state_tbl[i]&16) != 0 && *kp == SPK_KEY)
> +			if ((state_tbl[i] & 16) != 0 && *kp == SPK_KEY)
>  				continue;
>  			counters[*kp]++;
>  		}
> @@ -83,7 +83,7 @@ static void build_key_data(void)
>  		if (counters[i] == 0)
>  			continue;
>  		key_offsets[i] = offset;
> -		offset += (counters[i]+1);
> +		offset += (counters[i] + 1);
>  		if (offset >= MAXKEYS)
>  			break;
>  	}
> @@ -97,7 +97,7 @@ static void build_key_data(void)
>  			ch1 = *kp++;
>  			if (!ch1)
>  				continue;
> -			if ((state_tbl[i]&16) != 0 && ch1 == SPK_KEY)
> +			if ((state_tbl[i] & 16) != 0 && ch1 == SPK_KEY)
>  				continue;
>  			key = (state_tbl[i] << 8) + ch;
>  			counters[ch1]--;
> @@ -130,14 +130,14 @@ static int help_init(void)
>  	int i;
>  	int num_funcs = MSG_FUNCNAMES_END - MSG_FUNCNAMES_START + 1;
>  
> -	state_tbl = spk_our_keys[0]+SHIFT_TBL_SIZE+2;
> +	state_tbl = spk_our_keys[0] + SHIFT_TBL_SIZE + 2;
>  	for (i = 0; i < num_funcs; i++) {
>  		char *cur_funcname = spk_msg_get(MSG_FUNCNAMES_START + i);
>  
>  		if (start == *cur_funcname)
>  			continue;
>  		start = *cur_funcname;
> -		letter_offsets[(start&31)-1] = i;
> +		letter_offsets[(start & 31) - 1] = i;
>  	}
>  	return 0;
>  }
> @@ -160,12 +160,12 @@ int spk_handle_help(struct vc_data *vc, u_char type, u_char ch, u_short key)
>  		ch |= 32; /* lower case */
>  		if (ch < 'a' || ch > 'z')
>  			return -1;
> -		if (letter_offsets[ch-'a'] == -1) {
> +		if (letter_offsets[ch - 'a'] == -1) {
>  			synth_printf(spk_msg_get(MSG_NO_COMMAND), ch);
>  			synth_printf("\n");
>  			return 1;
>  		}
> -		cur_item = letter_offsets[ch-'a'];
> +		cur_item = letter_offsets[ch - 'a'];
>  	} else if (type == KT_CUR) {
>  		if (ch == 0
>  		    && (MSG_FUNCNAMES_START + cur_item + 1) <=
> @@ -186,7 +186,7 @@ int spk_handle_help(struct vc_data *vc, u_char type, u_char ch, u_short key)
>  		name = NULL;
>  		if ((type != KT_SPKUP) && (key > 0) && (key <= num_key_names)) {
>  			synth_printf("%s\n",
> -				spk_msg_get(MSG_KEYNAMES_START + key-1));
> +				spk_msg_get(MSG_KEYNAMES_START + key - 1));
>  			return 1;
>  		}
>  		for (i = 0; funcvals[i] != 0 && !name; i++) {
> @@ -195,7 +195,7 @@ int spk_handle_help(struct vc_data *vc, u_char type, u_char ch, u_short key)
>  		}
>  		if (!name)
>  			return -1;
> -		kp = spk_our_keys[key]+1;
> +		kp = spk_our_keys[key] + 1;
>  		for (i = 0; i < nstates; i++) {
>  			if (ch == kp[i])
>  				break;
> -- 
> 2.5.0
> 

      reply	other threads:[~2015-11-19 14:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 13:40 Christian Colic
2015-11-19 14:12 ` Luis de Bethencourt [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=20151119141203.GA25601@goodgumbo.baconseed.org \
    --to=luis@debethencourt.com \
    --cc=chris@the-brannons.com \
    --cc=colic.christian@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kirk@reisers.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samuel.thibault@ens-lyon.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

all inboxes | Powered by JetHome®