From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [platform-drivers-x86:linux-next 7/12] warning: (DRM_RADEON_KMS && DRM_I915 && STUB_POULSBO && F
Date: Mon, 20 Aug 2012 13:15:55 +0000 [thread overview]
Message-ID: <20120820131555.GA6601@localhost> (raw)
In-Reply-To: <20120818005028.GA5201@localhost>
On Mon, Aug 20, 2012 at 08:05:43AM -0500, Seth Forshee wrote:
> On Sat, Aug 18, 2012 at 08:50:28AM +0800, Fengguang Wu wrote:
> > Hi Seth,
> >
> > FYI, there are compile warnings in
> >
> > tree: git://cavan.codon.org.uk/platform-drivers-x86 linux-next
> > head: 973713edb3163c0386e36826166308f95adf87e4
> > commit: 16caa01ccb35a99f919143f78fb94d91426c45a4 [7/12] apple-gmux: Fix kconfig dependencies
> > config: i386-randconfig-b820 (attached as .config)
> >
> > All error/warnings:
> >
> > warning: (DRM_RADEON_KMS && DRM_I915 && STUB_POULSBO && FB_BACKLIGHT && USB_APPLEDISPLAY && FB_OLPC_DCON && ASUS_LAPTOP && SONY_LAPTOP && THINKPAD_ACPI && EEEPC_LAPTOP && ACPI_CMPC && SAMSUNG_Q10) selects BACKLIGHT_CLASS_DEVICE which has unmet direct dependencies (HAS_IOMEM && BACKLIGHT_LCD_SUPPORT)
> > warning: (DRM_NOUVEAU) selects ACPI_WMI which has unmet direct dependencies (X86 && X86_PLATFORM_DEVICES && ACPI)
> > warning: (DRM_NOUVEAU) selects MXM_WMI which has unmet direct dependencies (X86 && X86_PLATFORM_DEVICES && ACPI_WMI)
> > warning: (DRM_RADEON_KMS && DRM_I915 && STUB_POULSBO && FB_BACKLIGHT && USB_APPLEDISPLAY && FB_OLPC_DCON && ASUS_LAPTOP && SONY_LAPTOP && THINKPAD_ACPI && EEEPC_LAPTOP && ACPI_CMPC && SAMSUNG_Q10) selects BACKLIGHT_CLASS_DEVICE which has unmet direct dependencies (HAS_IOMEM && BACKLIGHT_LCD_SUPPORT)
> > warning: (DRM_NOUVEAU) selects ACPI_WMI which has unmet direct dependencies (X86 && X86_PLATFORM_DEVICES && ACPI)
> > warning: (DRM_NOUVEAU) selects MXM_WMI which has unmet direct dependencies (X86 && X86_PLATFORM_DEVICES && ACPI_WMI)
>
> Hi Fengguang,
>
> Why was this commit identified as producing these warnings? I can't see
> the relationship, and if I revert that commit or reset my HEAD to the
> commit just prior to that one I still see them. I get the same warnings
> in Linus's tree too, which doesn't have that commit.
Seth, yeah these may not related to the commit. In these warnings, I
see some "relation" between your tree name platform-drivers-x86 and
X86_PLATFORM_DEVICES, so decided to forward them to you.. Sorry if
this makes confusions/noises to you!
Thanks,
Fengguang
prev parent reply other threads:[~2012-08-20 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 0:50 [platform-drivers-x86:linux-next 7/12] warning: (DRM_RADEON_KMS && DRM_I915 && STUB_POULSBO && FB_BA Fengguang Wu
2012-08-20 13:05 ` [platform-drivers-x86:linux-next 7/12] warning: (DRM_RADEON_KMS && DRM_I915 && STUB_POULSBO && F Seth Forshee
2012-08-20 13:15 ` Fengguang Wu [this message]
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=20120820131555.GA6601@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@vger.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;
as well as URLs for NNTP newsgroup(s).