linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v4] Input: psxpad-spi - Add PSX (Play Station 1/2) pad SPI driver
Date: Sat, 29 Apr 2017 02:29:24 +0800	[thread overview]
Message-ID: <201704290207.x8Sx5eiy%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170428023137.6622-1-sylph23k@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1992 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-PSX-Play-Station-1-2-pad-SPI-driver/20170429-014135
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:496:5: warning: 'pdev' may be used uninitialized in this function [-Wmaybe-uninitialized]
     if (pdev) {
        ^

vim +/pdev +496 drivers/input//joystick/psxpad-spi.c

   480		/* pad settings */
   481		psxpad_setmotorlevel(pad, 0, 0);
   482	
   483		/* register input pool device */
   484		err = input_register_polled_device(pdev);
   485		if (err) {
   486			dev_err(&spi->dev, "psxpad-spi: probe: failed register!!\n");
   487			input_free_polled_device(pdev);
   488			goto err_free_mem;
   489		}
   490	
   491		pm_runtime_enable(&spi->dev);
   492	
   493		return 0;
   494	
   495	 err_free_mem:
 > 496		if (pdev) {
   497			psxpad_spi_deinit_ff(pad);
   498			input_free_polled_device(pdev);
   499		}
   500		devm_kfree(&spi->dev, pad);
   501	
   502		return err;
   503	}
   504	

---
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 --]

  reply	other threads:[~2017-04-28 18:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28  2:31 [PATCH v4] Input: psxpad-spi - Add PSX (Play Station 1/2) pad SPI driver Tomohiro Yoshidomi
2017-04-28 18:29 ` kbuild test robot [this message]
2017-04-28 22:04 ` Cameron Gutman
2017-04-29  1:35   ` Tomohiro Yoshidomi

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=201704290207.x8Sx5eiy%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;
as well as URLs for NNTP newsgroup(s).