mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: kbuild-all@01.org, Linus Walleij <linus.walleij@linaro.org>,
	Andrew Jeffery <andrew@aj.id.au>, Joel Stanley <joel@jms.id.au>,
	Alexandre Courbot <gnurou@gmail.com>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	openbmc@lists.ozlabs.org
Subject: Re: [PATCH] gpio: aspeed: Add debounce support
Date: Tue, 21 Feb 2017 00:36:14 +0800	[thread overview]
Message-ID: <201702210039.DP0X9QEg%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170220144004.10809-1-andrew@aj.id.au>

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

Hi Andrew,

[auto build test WARNING on next-20170220]
[cannot apply to gpio/for-next v4.9-rc8 v4.9-rc7 v4.9-rc6 v4.10]
[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/Andrew-Jeffery/gpio-aspeed-Add-debounce-support/20170220-231310
config: i386-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

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/gpio/gpio-aspeed.c: In function 'aspeed_gpio_set_config':
>> drivers/gpio/gpio-aspeed.c:733:9: warning: 'rc' may be used uninitialized in this function [-Wmaybe-uninitialized]
     return rc;
            ^~

vim +/rc +733 drivers/gpio/gpio-aspeed.c

   717		switch (param) {
   718		case PIN_CONFIG_INPUT_DEBOUNCE:
   719			rc = aspeed_gpio_set_debounce(chip, offset, arg);
   720			break;
   721		case PIN_CONFIG_BIAS_DISABLE:
   722		case PIN_CONFIG_BIAS_PULL_DOWN:
   723		case PIN_CONFIG_DRIVE_STRENGTH:
   724			rc = pinctrl_gpio_set_config(offset, config);
   725			break;
   726		case PIN_CONFIG_DRIVE_OPEN_DRAIN:
   727		case PIN_CONFIG_DRIVE_OPEN_SOURCE:
   728			/* Fallthrough for emulation, as per datasheet */
   729		default:
   730			rc = -ENOTSUPP;
   731		}
   732	
 > 733		return rc;
   734	}
   735	
   736	/*
   737	 * Any banks not specified in a struct aspeed_bank_props array are assumed to
   738	 * have the properties:
   739	 *
   740	 *     { .input = 0xffffffff, .output = 0xffffffff }
   741	 */

---
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: 58763 bytes --]

  reply	other threads:[~2017-02-20 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20 14:40 Andrew Jeffery
2017-02-20 16:36 ` kbuild test robot [this message]
2017-02-22  4:16 ` Joel Stanley
2017-02-22 13:49   ` Joel Stanley
2017-02-23  0:58   ` Andrew Jeffery

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=201702210039.DP0X9QEg%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=andrew@aj.id.au \
    --cc=gnurou@gmail.com \
    --cc=joel@jms.id.au \
    --cc=kbuild-all@01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.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

all inboxes | Powered by JetHome®