From: kbuild test robot <lkp@intel.com>
To: Tomohiro Yoshidomi <typesylph@gmail.com>
Cc: kbuild-all@01.org, dmitry.torokhov@gmail.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
sylph23k@gmail.com
Subject: Re: [PATCH v6] Input: psxpad-spi - Add PlayStation 1/2 joypads via SPI interface Driver
Date: Sun, 30 Apr 2017 12:17:40 +0800 [thread overview]
Message-ID: <201704301227.rqBiCDUe%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170430033522.14216-1-sylph23k@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2233 bytes --]
Hi Tomohiro,
[auto build test WARNING on input/next]
[also build test WARNING on v4.11-rc8 next-20170428]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Tomohiro-Yoshidomi/Input-psxpad-spi-Add-PlayStation-1-2-joypads-via-SPI-interface-Driver/20170430-114033
base: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 6.2.0
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=ia64
Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
All warnings (new ones prefixed by >>):
drivers/input/joystick/psxpad-spi.c: In function 'psxpad_spi_probe':
>> drivers/input/joystick/psxpad-spi.c:319:3: warning: 'err' may be used uninitialized in this function [-Wmaybe-uninitialized]
dev_err(&spi->dev,
^~~~~~~~~~~~~~~~~~
"%s: failed to pdev alloc mode: %d\n",
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
__func__, err);
~~~~~~~~~~~~~~
vim +/err +319 drivers/input/joystick/psxpad-spi.c
303 return 0;
304 }
305 #endif /* CONFIG_JOYSTICK_PSXPAD_SPI_FF */
306
307 static int psxpad_spi_probe(struct spi_device *spi)
308 {
309 struct psxpad *pad;
310 struct input_polled_dev *pdev;
311 struct input_dev *idev;
312 int err;
313
314 pad = devm_kzalloc(&spi->dev, sizeof(struct psxpad), GFP_KERNEL);
315 if (!pad)
316 return -ENOMEM;
317 pdev = input_allocate_polled_device();
318 if (!pdev) {
> 319 dev_err(&spi->dev,
320 "%s: failed to pdev alloc mode: %d\n",
321 __func__, err);
322 return -ENOMEM;
323 }
324
325 /* input poll device settings */
326 pad->pdev = pdev;
327 pad->spi = spi;
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 46788 bytes --]
next prev parent reply other threads:[~2017-04-30 4:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 3:35 Tomohiro Yoshidomi
2017-04-30 3:36 ` Tomohiro Yoshidomi
2017-04-30 4:17 ` kbuild test robot [this message]
2017-04-30 4:21 ` kbuild test robot
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=201704301227.rqBiCDUe%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sylph23k@gmail.com \
--cc=typesylph@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®