linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Felipe Balbi" <balbi@ti.com>,
	"Vladimir Zapolskiy" <vz@mleia.com>,
	"Russell King" <linux@arm.linux.org.uk>,
	"open list:OMAP SUPPORT" <linux-omap@vger.kernel.org>,
	"open list:ARM PORT" <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 03/10] arm: omap2: fix omap3 touchbook kconfig warning
Date: Thu, 22 Dec 2011 10:22:56 -0800	[thread overview]
Message-ID: <20111222182256.GO24444@atomide.com> (raw)
In-Reply-To: <1324341747-5922-4-git-send-email-felipe.contreras@gmail.com>

* Felipe Contreras <felipe.contreras@gmail.com> [111219 16:11]:
> warning: (MACH_OMAP3_TOUCHBOOK && DRM_RADEON_KMS && DRM_I915 && STUB_POULSBO && FB_BACKLIGHT && USB_APPLEDISPLAY && FB_OLPC_DCON && ASUS_LAPTOP && SONY_LAPTOP && THINKPAD_ACPI && EEEPC_LAPTOP && ACPI_ASUS && ACPI_CMPC && SAMSUNG_Q10) selects BACKLIGHT_CLASS_DEVICE which has unmet direct dependencies (HAS_IOMEM && BACKLIGHT_LCD_SUPPORT)
> 
> A lot of boards need BACKLIGHT_CLASS_DEVICE for the framebuffers to
> work, but it's not *needed* for the device itself. It might be nice to
> enable it by default somewhoe if graphics stuff is enabled, but that's
> another story.

Thanks applying into fixes-non-critical-part3.

Tony

  reply	other threads:[~2011-12-22 18:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1324341747-5922-1-git-send-email-felipe.contreras@gmail.com>
2011-12-20  0:42 ` [PATCH 01/10] arm: omap4: fix kconfig warning Felipe Contreras
2011-12-22 18:22   ` Tony Lindgren
2011-12-22 20:09     ` Felipe Contreras
2011-12-22 20:45       ` Tony Lindgren
2011-12-20  0:42 ` [PATCH 03/10] arm: omap2: fix omap3 touchbook " Felipe Contreras
2011-12-22 18:22   ` Tony Lindgren [this message]
2011-12-20  0:42 ` [PATCH 04/10] arm: omap2: fix regulator warnings Felipe Contreras
2011-12-22 18:23   ` Tony Lindgren

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=20111222182256.GO24444@atomide.com \
    --to=tony@atomide.com \
    --cc=balbi@ti.com \
    --cc=felipe.contreras@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=vz@mleia.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;
as well as URLs for NNTP newsgroup(s).