From: Corey Minyard <minyard@acm.org>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Jean Delvare <jdelvare@suse.de>,
Andy Lutomirski <luto@kernel.org>,
Corey Minyard <cminyard@mvista.com>
Subject: Re: [PATCH 2/4] dmi: Add a DMI firmware node and handling
Date: Fri, 29 Jan 2016 18:35:19 -0600 [thread overview]
Message-ID: <56AC0547.3040205@acm.org> (raw)
In-Reply-To: <201601300741.acyNBwIo%fengguang.wu@intel.com>
Dang, I've been doing too much Python. I've fixed this, but I guess I'll
wait for more comments.
-corey
On 01/29/2016 05:59 PM, kbuild test robot wrote:
> Hi Corey,
>
> [auto build test ERROR on char-misc/char-misc-testing]
> [also build test ERROR on v4.5-rc1 next-20160129]
> [if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
>
> url: https://github.com/0day-ci/linux/commits/minyard-acm-org/dmi-Rework-to-get-IPMI-autoloading-from-DMI-tables/20160130-074830
> config: i386-tinyconfig (attached as .config)
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All errors (new ones prefixed by >>):
>
> In file included from arch/x86/kernel/setup.c:46:0:
> include/linux/dmi.h: In function 'is_dmi_fwnode':
>>> include/linux/dmi.h:164:1: error: expected ';' before '}' token
> }
> ^
>
> vim +164 include/linux/dmi.h
>
> 158 static inline const struct dmi_system_id *
> 159 dmi_first_match(const struct dmi_system_id *list) { return NULL; }
> 160
> 161 static inline bool is_dmi_fwnode(struct fwnode_handle *fwnode)
> 162 {
> 163 return false
> > 164 }
> 165
> 166 static inline struct dmi_fwnode *to_dmi_device(struct fwnode_handle *fwnode)
> 167 {
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2016-01-30 1:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 22:43 [PATCH 0/4] dmi: Rework to get IPMI autoloading from DMI tables minyard
2016-01-29 22:43 ` [PATCH 1/4] dmi: remove const from return of dmi_find_device minyard
2016-01-29 22:43 ` [PATCH 2/4] dmi: Add a DMI firmware node and handling minyard
2016-01-29 23:59 ` kbuild test robot
2016-01-30 0:35 ` Corey Minyard [this message]
2016-01-30 0:41 ` kbuild test robot
2016-01-31 22:46 ` Andy Lutomirski
2016-02-01 0:36 ` Corey Minyard
2016-02-01 9:25 ` Jean Delvare
2016-02-02 13:37 ` Corey Minyard
2016-02-02 18:25 ` Andy Lutomirski
2016-02-03 16:51 ` Corey Minyard
2016-01-29 22:43 ` [PATCH 3/4] dmi: Move IPMI DMI scanning to the DMI code minyard
2016-01-29 22:43 ` [PATCH 4/4] dmi/ipmi: Add IPMI DMI devices as platform devices minyard
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=56AC0547.3040205@acm.org \
--to=minyard@acm.org \
--cc=cminyard@mvista.com \
--cc=jdelvare@suse.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luto@kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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
Powered by JetHome