mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Allen Hung <allen_hung@dell.com>
Cc: kbuild-all@01.org, Jean Delvare <jdelvare@suse.com>,
	linux-kernel@vger.kernel.org,
	Mario Limonciello <mario_limonciello@dell.com>,
	Allen Hung <allen_hung@dell.com>
Subject: Re: [PATCH 2/2] dmi-id: add dmi/id/oem group for exporting oem strings to sysfs
Date: Thu, 14 Jul 2016 17:16:27 +0800	[thread overview]
Message-ID: <201607141715.vw8AXpMK%fengguang.wu@intel.com> (raw)
In-Reply-To: <1468483283-84766-3-git-send-email-allen_hung@dell.com>

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

Hi,

[auto build test ERROR on v4.7-rc7]
[also build test ERROR on next-20160713]
[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/Allen-Hung/dmi-id-export-oem-strings-to-sysfs/20160714-161631
config: i386-defconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   drivers/firmware/dmi-id.c: In function 'dmi_id_init_oem_attr_group':
>> drivers/firmware/dmi-id.c:107:28: error: 'dmi_dev' undeclared (first use in this function)
     ret = sysfs_create_group(&dmi_dev->kobj, &dmi_oem_attr_group);
                               ^~~~~~~
   drivers/firmware/dmi-id.c:107:28: note: each undeclared identifier is reported only once for each function it appears in

vim +/dmi_dev +107 drivers/firmware/dmi-id.c

   101		int i, ret;
   102		const struct dmi_device *dev;
   103		struct dmi_oem_attribute *oa, *tmp;
   104		struct device_attribute dev_attr_tmpl =
   105			__ATTR(, 0444, sys_dmi_oem_show, NULL);
   106	
 > 107		ret = sysfs_create_group(&dmi_dev->kobj, &dmi_oem_attr_group);
   108		if (ret)
   109			return ret;
   110	

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

  reply	other threads:[~2016-07-14  9:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14  8:01 [PATCH 0/2] dmi-id: export " Allen Hung
2016-07-14  8:01 ` [PATCH 1/2] dmi-id: don't free dev structure after calling device_register Allen Hung
2016-07-18 17:09   ` Jean Delvare
2016-07-14  8:01 ` [PATCH 2/2] dmi-id: add dmi/id/oem group for exporting oem strings to sysfs Allen Hung
2016-07-14  9:16   ` kbuild test robot [this message]
2016-07-19  9:03   ` Jean Delvare
2016-07-19 14:47     ` Mario_Limonciello
2016-08-02 13:43       ` Jean Delvare
2016-08-02 18:56         ` Mario_Limonciello
2016-08-15  9:55           ` Allen Hung
2016-08-24  8:05             ` Allen Hung
2016-07-26 21:03     ` Mario_Limonciello
2016-07-29  9:59       ` Allen Hung
2016-07-15  9:42 [PATCH 0/2] dmi-id: export " Allen Hung
2016-07-15  9:42 ` [PATCH 2/2] dmi-id: add dmi/id/oem group for exporting " Allen Hung

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=201607141715.vw8AXpMK%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=allen_hung@dell.com \
    --cc=jdelvare@suse.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario_limonciello@dell.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

all inboxes | Powered by JetHome®