mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <shuahkhan@gmail.com>
To: mingo@redhat.com
Cc: shuahkhan@gmail.com, hpa@zytor.com, tglx@linutronix.de,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] x86: kernel/check.c simple_strtoul cleanup
Date: Mon, 14 May 2012 09:01:40 -0600	[thread overview]
Message-ID: <1337007700.2476.1.camel@lorien2> (raw)
In-Reply-To: <1336326908.2897.12.camel@lorien2>

On Sun, 2012-05-06 at 11:55 -0600, Shuah Khan wrote:
> Change set_corruption_check() and set_corruption_check_period()
> in kernel/check.c to call kstrtoul() instead of calling
> obsoleted simple_strtoul().

How about this patch? Are you not interested in this type of cleanup
patches? Looking for some feedback so I can spend my energies on
something that would be worth while in the future :)

-- Shuah
> 
> 
> Signed-off-by: Shuah Khan <shuahkhan@gmail.com>
> ---
>  arch/x86/kernel/check.c |   20 ++++++++++++++------
>  1 files changed, 14 insertions(+), 6 deletions(-)
> 
> diff --git a/arch/x86/kernel/check.c b/arch/x86/kernel/check.c
> index 5da1269..e2dbcb7 100644
> --- a/arch/x86/kernel/check.c
> +++ b/arch/x86/kernel/check.c
> @@ -27,21 +27,29 @@ static int num_scan_areas;
>  
>  static __init int set_corruption_check(char *arg)
>  {
> -	char *end;
> +	ssize_t ret;
> +	unsigned long val;
>  
> -	memory_corruption_check = simple_strtol(arg, &end, 10);
> +	ret = kstrtoul(arg, 10, &val);
> +	if (ret)
> +		return ret;
>  
> -	return (*end == 0) ? 0 : -EINVAL;
> +	memory_corruption_check = val;
> +	return 0;
>  }
>  early_param("memory_corruption_check", set_corruption_check);
>  
>  static __init int set_corruption_check_period(char *arg)
>  {
> -	char *end;
> +	ssize_t ret;
> +	unsigned long val;
>  
> -	corruption_check_period = simple_strtoul(arg, &end, 10);
> +	ret = kstrtoul(arg, 10, &val);
> +	if (ret)
> +		return ret;
>  
> -	return (*end == 0) ? 0 : -EINVAL;
> +	corruption_check_period = val;
> +	return 0;
>  }
>  early_param("memory_corruption_check_period", set_corruption_check_period);
>  



  reply	other threads:[~2012-05-14 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-06 17:55 Shuah Khan
2012-05-14 15:01 ` Shuah Khan [this message]
2012-05-16 21:43 ` [tip:x86/cleanups] " tip-bot for Shuah Khan

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=1337007700.2476.1.camel@lorien2 \
    --to=shuahkhan@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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