From: Maciek Borzecki <maciek.borzecki@gmail.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <j.anaszewski@samsung.com>,
linux-leds@vger.kernel.org, linux-doc@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 2/3] leds: add debugfs to device trigger
Date: Tue, 29 Sep 2015 09:04:25 +0200 [thread overview]
Message-ID: <20150929070425.GA2896@corsair.lan> (raw)
In-Reply-To: <201509291106.01PhMygT%fengguang.wu@intel.com>
On 09/29 11:41, kbuild test robot wrote:
> Hi Maciek,
>
> [auto build test results on v4.3-rc3 -- if it's inappropriate base, please ignore]
>
> reproduce:
> # apt-get install sparse
> make ARCH=x86_64 allmodconfig
> make C=1 CF=-D__CHECK_ENDIAN__
>
>
> sparse warnings: (new ones prefixed by >>)
>
> >> drivers/leds/trigger/ledtrig-device.c:214:22: sparse: incorrect type in argument 1 (different address spaces)
> drivers/leds/trigger/ledtrig-device.c:214:22: expected char const *<noident>
> drivers/leds/trigger/ledtrig-device.c:214:22: got char const [noderef] <asn:1>*buf
Right, noted right after sending the patch. Will fix in v2.
>
> vim +214 drivers/leds/trigger/ledtrig-device.c
>
> 198 .read = seq_read,
> 199 .llseek = seq_lseek,
> 200 .release = single_release
> 201 };
> 202
> 203 static int get_dev_from_user(const char __user *buf, size_t size,
> 204 dev_t *dev)
> 205 {
> 206 unsigned int major;
> 207 unsigned int minor;
> 208 int ret;
> 209
> 210 WARN_ON(dev == NULL);
> 211 if (dev == NULL)
> 212 return -EINVAL;
> 213
> > 214 ret = sscanf(buf, "%u:%u", &major, &minor);
> 215 if (ret < 2)
> 216 return -EINVAL;
> 217
> 218 *dev = MKDEV(major, minor);
> 219 return 0;
> 220 }
> 221
> 222 static ssize_t ledtrig_dev_register_write(struct file *filp,
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
--
Maciek Borzecki
next prev parent reply other threads:[~2015-09-29 7:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 20:43 [PATCH 0/3] leds: add device trigger Maciek Borzecki
[not found] ` <cover.1443472356.git.maciek.borzecki@gmail.com>
2015-09-28 20:43 ` [PATCH 1/3] leds: add device activity LED triggers Maciek Borzecki
2015-09-28 20:43 ` [PATCH 2/3] leds: add debugfs to device trigger Maciek Borzecki
2015-09-29 3:41 ` kbuild test robot
2015-09-29 3:41 ` kbuild test robot
2015-09-29 7:04 ` Maciek Borzecki [this message]
2015-09-30 14:08 ` Jacek Anaszewski
2015-09-30 15:47 ` Maciek Borzecki
2015-10-01 7:36 ` Jacek Anaszewski
2015-11-15 11:22 ` Pavel Machek
2015-09-28 20:43 ` [PATCH 3/3] Documentation: leds: document ledtrig-device trigger Maciek Borzecki
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=20150929070425.GA2896@corsair.lan \
--to=maciek.borzecki@gmail.com \
--cc=corbet@lwn.net \
--cc=j.anaszewski@samsung.com \
--cc=kbuild-all@01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rpurdie@rpsys.net \
/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.