From: Darren Hart <dvhart@infradead.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Mario Limonciello <mario.limonciello@dell.com>,
kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: drivers/platform/x86/dell-smbios-smm.c:99: undefined reference to `dcdbas_smi_request'
Date: Tue, 20 Mar 2018 16:24:53 -0700 [thread overview]
Message-ID: <20180320232453.GA24376@fury> (raw)
In-Reply-To: <201803201222.K37oCZ9Z%fengguang.wu@intel.com>
On Tue, Mar 20, 2018 at 12:47:24PM +0800, kbuild test robot wrote:
> Hi Mario,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 1b5f3ba415fe4cf8b8b39c8d104ed44cde330658
> commit: 25d47027e1003546bfd8964b4423cb39bc2d53e9 platform/x86: dell-smbios: Link all dell-smbios-* modules together
For completeness:
This is a known warning at this commit, which is addressed in future commits now
merged, specifically:
75073a64a98c platform/x86: dell-smbios: Resolve dependency error on ACPI_WMI
32d7b19bad96 platform/x86: dell-smbios: Resolve dependency error on DCDBAS
329d58b890be platform/x86: Allow for SMBIOS backend defaults
Thanks,
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2018-03-20 23:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 4:47 drivers/platform/x86/dell-smbios-smm.c:99: undefined reference to `dcdbas_smi_request' kbuild test robot
2018-03-20 23:24 ` Darren Hart [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-12 9:28 kbuild test robot
2018-05-12 18:32 ` Darren Hart
2018-05-12 18:51 ` Randy Dunlap
2018-05-12 19:15 ` Darren Hart
2018-05-12 20:04 ` Randy Dunlap
2018-05-04 18:24 kbuild test robot
2018-05-04 18:27 ` Mario.Limonciello
2018-05-04 20:08 ` dvhart
2018-05-04 20:15 ` Darren Hart
2018-05-06 22:29 ` Darren Hart
2018-04-26 12:13 kbuild test robot
2018-04-26 12:58 ` Mario.Limonciello
2018-03-14 3:56 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=20180320232453.GA24376@fury \
--to=dvhart@infradead.org \
--cc=fengguang.wu@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.