From: Jinyoung Park <jinyoungp@nvidia.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: aat2870 causes build failure in current upstream
Date: Fri, 5 Aug 2011 15:03:46 +0900 [thread overview]
Message-ID: <4E3B87C2.3020304@nvidia.com> (raw)
In-Reply-To: <20110804171725.GA12729@elte.hu>
Hi,
I try to check allmodconfig error issue for aat2870 backlight driver.
But I could not observing error message what you attached, building is
successed.
Please let me know how to reproduce allmodconfig problem for aat2870
backlight driver.
This is my repro step.
$ git clone
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
$ cd linux-next
$ make allmodconfig
$ make
Thanks,
Jin.
2011-08-05 오전 2:17, Ingo Molnar 쓴 글:
>
> * H. Peter Anvin<hpa@zytor.com> wrote:
>
>> Doing an "allmodconfig" on i386:
>>
>> drivers/built-in.o: In function `aat2870_bl_remove':
>> /home/hpa/kernel/git.test/drivers/video/backlight/aat2870_bl.c:217:
>> undefined reference to `backlight_device_unregister'
>> drivers/built-in.o: In function `aat2870_bl_probe':
>> /home/hpa/kernel/git.test/drivers/video/backlight/aat2870_bl.c:159:
>> undefined reference to `backlight_device_register'
>> /home/hpa/kernel/git.test/drivers/video/backlight/aat2870_bl.c:201:
>> undefined reference to `backlight_device_unregister'
>> make[2]: *** [.tmp_vmlinux1] Error 1
>> make[1]: *** [sub-make] Error 2
>> make[1]: Leaving directory `/home/hpa/kernel/git.test'
>
> The allmodconfig build is still broken upstream.
>
> Thanks,
>
> Ingo
next prev parent reply other threads:[~2011-08-05 6:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 20:17 aat2870 causes build failure in current upstream H. Peter Anvin
2011-08-04 17:17 ` Ingo Molnar
2011-08-05 6:03 ` Jinyoung Park [this message]
2011-08-05 16:22 ` H. Peter Anvin
2011-08-06 0:38 ` Randy Dunlap
2011-08-06 6:53 ` Ingo Molnar
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=4E3B87C2.3020304@nvidia.com \
--to=jinyoungp@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
/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