mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Sebastian Reichel <sre@kernel.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Sebastian Reichel <sre@kernel.org>,
	Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] power: move power supply drivers to power/supply
Date: Sat, 18 Jun 2016 20:18:59 +0800	[thread overview]
Message-ID: <201606182052.MDTWFvcT%fengguang.wu@intel.com> (raw)
In-Reply-To: <1466169932-28031-2-git-send-email-sre@kernel.org>

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

Hi,

[auto build test WARNING on battery/master]
[also build test WARNING on v4.7-rc3 next-20160617]
[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/Sebastian-Reichel/Move-power-supply-subsystem-to-drivers-power-supply/20160617-213931
base:   git://git.infradead.org/battery-2.6.git master
config: s390-allyesconfig (attached as .config)
compiler: s390x-linux-gnu-gcc (Debian 5.3.1-8) 5.3.1 20160205
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=s390 

All warnings (new ones prefixed by >>):

   drivers/power/supply/da9150-fg.c: In function 'da9150_fg_read_attr.isra.1':
>> drivers/power/supply/da9150-fg.c:108:1: warning: 'da9150_fg_read_attr.isra.1' uses dynamic stack allocation
    }
    ^

vim +108 drivers/power/supply/da9150-fg.c

a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07   92  static u32 da9150_fg_read_attr(struct da9150_fg *fg, u8 code, u8 size)
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07   93  
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07   94  {
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07   95  	u8 buf[size];
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07   96  	u8 read_addr;
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07   97  	u32 res = 0;
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07   98  	int i;
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07   99  
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07  100  	/* Set QIF code (READ mode) */
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07  101  	read_addr = (code & DA9150_QIF_CODE_MASK) | DA9150_QIF_READ;
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07  102  
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07  103  	da9150_read_qif(fg->da9150, read_addr, size, buf);
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07  104  	for (i = 0; i < size; ++i)
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07  105  		res |= (buf[i] << (i * DA9150_QIF_BYTE_SIZE));
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07  106  
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07  107  	return res;
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07 @108  }
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07  109  
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07  110  static void da9150_fg_write_attr(struct da9150_fg *fg, u8 code, u8 size,
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07  111  				 u32 val)
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07  112  
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07  113  {
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07  114  	u8 buf[size];
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07  115  	u8 write_addr;
a419b4fd drivers/power/da9150-fg.c Adam Thomson 2015-10-07  116  	int i;

:::::: The code at line 108 was first introduced by commit
:::::: a419b4fd9138c6cd5049d14813e7d94e596e4540 power: Add support for DA9150 Fuel-Gauge

:::::: TO: Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
:::::: CC: Lee Jones <lee.jones@linaro.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/octet-stream, Size: 41729 bytes --]

  reply	other threads:[~2016-06-18 12:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-17 13:25 [PATCH 0/2] Move power supply subsystem to drivers/power/supply Sebastian Reichel
2016-06-17 13:25 ` [PATCH 1/2] power: move power supply drivers to power/supply Sebastian Reichel
2016-06-18 12:18   ` kbuild test robot [this message]
2016-06-17 13:25 ` [PATCH 2/2] power/supply: unify DT documentation Sebastian Reichel

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=201606182052.MDTWFvcT%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=dbaryshkov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sre@kernel.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®