All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Toon Schoenmakers <nighteyes1993@gmail.com>
Cc: sjakub@gmail.com, gregkh@suse.de, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: asus_oled: Fixed checkpatch.pl warnings in asus_oled.c
Date: Thu, 22 Dec 2011 09:42:11 +0300	[thread overview]
Message-ID: <20111222064211.GH26771@mwanda> (raw)
In-Reply-To: <1324386035.27425.2.camel@RainbowDash>

[-- Attachment #1: Type: text/plain, Size: 1724 bytes --]

On Tue, Dec 20, 2011 at 02:00:33PM +0100, Toon Schoenmakers wrote:
> >From ac6a96cdf890714ec7b8f0e6597f82a49cfbe232 Mon Sep 17 00:00:00 2001
> From: Toon Schoenmakers <nighteyes1993@gmail.com>
> Date: Tue, 20 Dec 2011 13:52:41 +0100
> Subject: [PATCH] staging: asus_oled: Fixed checkpatch.pl warnings in
> asus_oled.c
> 

Insufficient patch description.

Patch mangled.  Read Documentation/email-clients.txt send it to
yourself, verify that it applies with `git am`.

> Signed-off-by: Toon Schoenmakers <nighteyes1993@gmail.com>
> ---
> drivers/staging/asus_oled/asus_oled.c |    4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/asus_oled/asus_oled.c
> b/drivers/staging/asus_oled/asus_oled.c
> index 7bb7da7..e77e4e0 100644
> --- a/drivers/staging/asus_oled/asus_oled.c
> +++ b/drivers/staging/asus_oled/asus_oled.c
> @@ -201,7 +201,7 @@ static ssize_t set_enabled(struct device *dev,
> struct device_attribute *attr,
> struct usb_interface *intf = to_usb_interface(dev);
> struct asus_oled_dev *odev = usb_get_intfdata(intf);
> unsigned long value;
> - if (strict_strtoul(buf, 10, &value))
> + if (kstrtoul(buf, 10, &value))

We introduced a lot of new functions here so it's not just a one to
one translation from the old strict_strtoul().  For example
kstrtou8() might be more appropriate here because that's what gets
passed to enable_oled().  You would need to change the type for
value as well.

Althought it doesn't matter much.  If the user passes anything
besides 1 or 0, they deserve what they get I suppose.

Preserve the error code instead of returning -EINVAL for everything.

> return -EINVAL;

regards,
dan carpenter


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2011-12-22  6:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20 13:00 [PATCH] staging: asus_oled: Fixed checkpatch.pl warnings in asus_oled.c Toon Schoenmakers
2011-12-22  6:42 ` Dan Carpenter [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=20111222064211.GH26771@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nighteyes1993@gmail.com \
    --cc=sjakub@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.