public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Liam Breck <liam@networkimprov.net>
Cc: kbuild-all@01.org, Sebastian Reichel <sre@kernel.org>,
	linux-pm@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
	Hans de Goede <hdegoede@redhat.com>,
	Liam Breck <kernel@networkimprov.net>
Subject: Re: [PATCH v2] power: bq24190_charger: Uniform pm_runtime_get() failure handling
Date: Thu, 30 Mar 2017 02:01:45 +0800	[thread overview]
Message-ID: <201703300123.q3wpYzfw%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170329014913.3970-1-liam@networkimprov.net>

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

Hi Liam,

[auto build test ERROR on next-20170328]
[cannot apply to battery/master power-supply/next v4.9-rc8 v4.9-rc7 v4.9-rc6 v4.11-rc4]
[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/Liam-Breck/power-bq24190_charger-Uniform-pm_runtime_get-failure-handling/20170330-002331
config: i386-randconfig-x013-201713 (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 

All errors (new ones prefixed by >>):

   drivers/power/supply/bq24190_charger.c: In function 'bq24190_probe':
>> drivers/power/supply/bq24190_charger.c:1505:4: error: label 'out5' used but not defined
       goto out5;
       ^~~~

vim +/out5 +1505 drivers/power/supply/bq24190_charger.c

4db249b6 Hans de Goede 2017-03-23  1499  	if (bdi->extcon) {
4db249b6 Hans de Goede 2017-03-23  1500  		INIT_DELAYED_WORK(&bdi->extcon_work, bq24190_extcon_work);
4db249b6 Hans de Goede 2017-03-23  1501  		bdi->extcon_nb.notifier_call = bq24190_extcon_event;
4db249b6 Hans de Goede 2017-03-23  1502  		ret = devm_extcon_register_notifier(dev, bdi->extcon, -1,
4db249b6 Hans de Goede 2017-03-23  1503  						    &bdi->extcon_nb);
4db249b6 Hans de Goede 2017-03-23  1504  		if (ret)
4db249b6 Hans de Goede 2017-03-23 @1505  			goto out5;
4db249b6 Hans de Goede 2017-03-23  1506  
4db249b6 Hans de Goede 2017-03-23  1507  		/* Sync initial cable state */
4db249b6 Hans de Goede 2017-03-23  1508  		queue_delayed_work(system_wq, &bdi->extcon_work, 0);

:::::: The code at line 1505 was first introduced by commit
:::::: 4db249b6f3b47c28c361cf8598954b12403ce94c power: supply: bq24190_charger: Use extcon to determine ilimit, 5v boost

:::::: TO: Hans de Goede <hdegoede@redhat.com>
:::::: CC: Sebastian Reichel <sre@kernel.org>

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

      parent reply	other threads:[~2017-03-29 18:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29  1:49 [PATCH v2] power: bq24190_charger: Uniform pm_runtime_get() failure handling Liam Breck
2017-03-29 16:30 ` Tony Lindgren
2017-03-29 18:01 ` kbuild test robot [this message]

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=201703300123.q3wpYzfw%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=kernel@networkimprov.net \
    --cc=liam@networkimprov.net \
    --cc=linux-pm@vger.kernel.org \
    --cc=sre@kernel.org \
    --cc=tony@atomide.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