mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Richard Tresidder <rtresidd@electromag.com.au>
Cc: kbuild-all@01.org, sre@kernel.org, enric.balletbo@collabora.com,
	ncrews@chromium.org, andrew.smirnov@gmail.com,
	groeck@chromium.org, david@lechnology.com,
	rtresidd@electromag.com.au, tglx@linutronix.de,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] power/supply/powersupply_sysfs: Add of_node name to uevent message if available
Date: Sat, 27 Jul 2019 04:45:07 +0800	[thread overview]
Message-ID: <201907270451.FVsMeeYH%lkp@intel.com> (raw)
In-Reply-To: <1564040858-24202-1-git-send-email-rtresidd@electromag.com.au>

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

Hi Richard,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v5.3-rc1 next-20190726]
[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/Richard-Tresidder/power-supply-powersupply_sysfs-Add-of_node-name-to-uevent-message-if-available/20190727-033750
config: arm-omap2plus_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.4.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=7.4.0 make.cross ARCH=arm 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   drivers/power/supply/power_supply_sysfs.c: In function 'power_supply_uevent':
>> drivers/power/supply/power_supply_sysfs.c:400:22: error: dereferencing pointer to incomplete type 'struct device_node'
             psy->of_node->name);
                         ^~

vim +400 drivers/power/supply/power_supply_sysfs.c

   381	
   382	int power_supply_uevent(struct device *dev, struct kobj_uevent_env *env)
   383	{
   384		struct power_supply *psy = dev_get_drvdata(dev);
   385		int ret = 0, j;
   386		char *prop_buf;
   387		char *attrname;
   388	
   389		if (!psy || !psy->desc) {
   390			dev_dbg(dev, "No power supply yet\n");
   391			return ret;
   392		}
   393	
   394		ret = add_uevent_var(env, "POWER_SUPPLY_NAME=%s", psy->desc->name);
   395		if (ret)
   396			return ret;
   397	
   398		if (psy->of_node) {
   399			ret = add_uevent_var(env, "POWER_SUPPLY_OF_NODE_NAME=%s",
 > 400					     psy->of_node->name);

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

  parent reply	other threads:[~2019-07-26 20:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25  7:47 Richard Tresidder
2019-07-25 14:08 ` David Lechner
2019-07-26  2:40   ` Richard Tresidder
2019-07-26 20:45 ` kbuild test robot [this message]
2019-07-29  8:32 ` 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=201907270451.FVsMeeYH%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrew.smirnov@gmail.com \
    --cc=david@lechnology.com \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@chromium.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=ncrews@chromium.org \
    --cc=rtresidd@electromag.com.au \
    --cc=sre@kernel.org \
    --cc=tglx@linutronix.de \
    /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®