public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <wfg@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Inki Dae <inki.dae@samsung.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Compile error: drivers/video/backlight/lcd.c:35:7: error: ‘FB_EARLY_EVENT_BLANK’ undeclared (first use in this function)
Date: Thu, 24 May 2012 20:42:28 +0800	[thread overview]
Message-ID: <20120524124228.GA20635@localhost> (raw)
In-Reply-To: <20120523132941.befd211c.akpm@linux-foundation.org>

On Wed, May 23, 2012 at 01:29:41PM -0700, Andrew Morton wrote:
> On Wed, 23 May 2012 19:13:29 +0800
> wfg@linux.intel.com wrote:
> 
> > tree:   git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git akpm
> > head:   900cd0fca590e51f720f44f63082b7934d0ff42d
> > commit: 07e86d6ba94cc94da2463521ef3def43ed55607d (180/308)
> > config: i386-randconfig-mm1
> > 
> > drivers/video/backlight/lcd.c:35:7: error: ‘FB_EARLY_EVENT_BLANK’ undeclared (first use in this function)
> > drivers/video/backlight/lcd.c:35:7: note: each undeclared identifier is reported only once for each function it appears in
> > drivers/video/backlight/lcd.c:36:7: error: ‘FB_R_EARLY_EVENT_BLANK’ undeclared (first use in this function)
> > 
> > Andrew, this should be fixable by moving the immediately following
> > patch "fbdev: add events for early fb event support" before this one.
> 
> Whoa.  What are you actually doing over there?  A build test for each and every
> patch in linux-next?  Impressed!

Yup.  I've been running 32 CPU cores all day&night, which build tests
~1300 commits and creates ~25000 kernel images each day.

To be exact, I'm build testing the akpm-base..akpm part of linux-next.
For the other parts of linux-next, I'm directly build testing the
trees/branches that linux-next pulls from, so as to find problems and
give feedback to the developers *ASAP*. The ultimate goal is to build
test each and every commit once they hit any topic/test branch,
hopefully before they are merged into some for-next branches.

The build test system is still catching up to test lots of old commits
and build up database of "known" build errors and warnings. Once
ready, I'll switch it into auto email notification mode. So in future,
when someone "git push" new patches, he will likely receive emails about
new build errors/warnings (if there are any) in one hour.

Thanks,
Fengguang

           reply	other threads:[~2012-05-24 12:42 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20120523132941.befd211c.akpm@linux-foundation.org>]

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=20120524124228.GA20635@localhost \
    --to=wfg@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=inki.dae@samsung.com \
    --cc=linux-kernel@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