linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: gshark <gshark.jeong@gmail.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	linux-next@vger.kernel.org, Daniel Jeong <daniel.jeong@ti.com>
Subject: Re: mmotm 2012-09-06-16-46 uploaded (drivers/video/backlight/lm3639_bl)
Date: Mon, 10 Sep 2012 09:11:11 +0900	[thread overview]
Message-ID: <504D301F.60209@gmail.com> (raw)
In-Reply-To: <504A93D3.7060203@xenotime.net>

Hi Randy.

LM3630/9 have the pins for led so these depend on BACKLIGHT_CLASS_DEVICE 
and I2C.
So we need to set LEDS_CLASS and NEW_LEDS.

I will put these two into driver/video/backlight/Kconfig file and patch 
it so that you don't need to do it.

2012년 09월 08일 09:39, Randy Dunlap 쓴 글:
> On 09/06/2012 04:47 PM, akpm@linux-foundation.org wrote:
>
>> The mm-of-the-moment snapshot 2012-09-06-16-46 has been uploaded to
>>
>>     http://www.ozlabs.org/~akpm/mmotm/
>>
>
> on x86_64:
>
> ERROR: "led_classdev_register" [drivers/video/backlight/lm3639_bl.ko] undefined!
> ERROR: "led_classdev_unregister" [drivers/video/backlight/lm3639_bl.ko] undefined!
>
> Full randconfig file is attached.
>

  reply	other threads:[~2012-09-10  0:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06 23:47 mmotm 2012-09-06-16-46 uploaded akpm
2012-09-07 15:12 ` Michal Hocko
2012-09-07 15:22   ` Fengguang Wu
2012-09-07 15:23     ` Michal Hocko
2012-09-07 23:45 ` mmotm 2012-09-06-16-46 uploaded (fs/binfmt_aout) Randy Dunlap
2012-09-11 22:17   ` Andrew Morton
2012-09-08  0:39 ` mmotm 2012-09-06-16-46 uploaded (drivers/video/backlight/lm3639_bl) Randy Dunlap
2012-09-10  0:11   ` gshark [this message]
2012-09-08  0:50 ` mmotm 2012-09-06-16-46 uploaded (drivers/misc/lis3lv02d/lis3lv02d_spi.c) Randy Dunlap
2012-09-08 10:44   ` Daniel Mack

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=504D301F.60209@gmail.com \
    --to=gshark.jeong@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=daniel.jeong@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@xenotime.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;
as well as URLs for NNTP newsgroup(s).