From: Randy Dunlap <rdunlap@xenotime.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jinyoung Park <jinyoungp@nvidia.com>, Ingo Molnar <mingo@elte.hu>,
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 17:38:57 -0700 [thread overview]
Message-ID: <20110805173857.b1a23e59.rdunlap@xenotime.net> (raw)
In-Reply-To: <4E3C18D7.9070303@zytor.com>
On Fri, 05 Aug 2011 09:22:47 -0700 H. Peter Anvin wrote:
> On 08/04/2011 11:03 PM, Jinyoung Park wrote:
> > 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.
> >
>
> Get Linus' current tree, not linux-next.
Now fixed? current mainline i386 allmodconfig builds OK for me.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-08-06 0:39 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
2011-08-05 16:22 ` H. Peter Anvin
2011-08-06 0:38 ` Randy Dunlap [this message]
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=20110805173857.b1a23e59.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jinyoungp@nvidia.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 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.