From: Julijonas Kikutis <julijonas.kikutis@gmail.com>
To: Darren Hart <dvhart@infradead.org>
Cc: Corentin Chary <corentin.chary@gmail.com>,
"open list:ABI/API" <linux-api@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:SAMSUNG LAPTOP DR..."
<platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH v2] samsung-laptop: enable better lid handling
Date: Thu, 29 Jan 2015 13:12:52 +0000 [thread overview]
Message-ID: <1422537172.1835.4.camel@gmail.com> (raw)
In-Reply-To: <20150129052021.GA115032@vmdeb7>
> Patch is generally fine, thanks for addressing my comments. Prior to merging I
> always run checkpatch.pl just in case I missed anything obvious:
>
> $ scripts/checkpatch.pl ~/samsung/01-lid-handling.patch
> WARNING: Prefer kstrto<type> to single variable sscanf
> #219: FILE: drivers/platform/x86/samsung-laptop.c:900:
> + if (!count || sscanf(buf, "%i", &value) != 1)
> + return -EINVAL;
>
> total: 0 errors, 1 warnings, 219 lines checked
>
> Please always run checkpatch.pl. It isn't sufficient and doesn't catch
> everything, but it is a minimum bar kind of thing.
I did run checkpatch.pl but left sscanf to be consistent with
set_battery_life_extender and set_usb_charge functions. Nevertheless, I
have just sent the third version of the patch with sscanf changed to
kstrtoint.
Thank you.
Julijonas
next prev parent reply other threads:[~2015-01-29 13:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 21:18 [PATCH] samsung-laptop: enable better lid handling Julijonas Kikutis
2015-01-27 2:52 ` Darren Hart
2015-01-27 9:54 ` Corentin Chary
2015-01-27 13:35 ` Julijonas Kikutis
2015-01-27 13:26 ` [PATCH v2] " Julijonas Kikutis
2015-01-29 5:20 ` Darren Hart
2015-01-29 13:12 ` Julijonas Kikutis [this message]
2015-01-29 13:04 ` [PATCH v3] " Julijonas Kikutis
2015-02-07 2:38 ` Darren Hart
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=1422537172.1835.4.camel@gmail.com \
--to=julijonas.kikutis@gmail.com \
--cc=corentin.chary@gmail.com \
--cc=dvhart@infradead.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).