From: Richard Purdie <rpurdie@rpsys.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Matthew Garrett <mjg@redhat.com>,
Haojian Zhuang <haojian.zhuang@marvell.com>,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: linux-next: build failure after merge of the final tree (backlight related)
Date: Thu, 11 Mar 2010 09:36:10 -0800 [thread overview]
Message-ID: <1268328970.1625.2.camel@rex> (raw)
In-Reply-To: <20100310180343.c6305829.sfr@canb.auug.org.au>
Hi,
On Wed, 2010-03-10 at 18:03 +1100, Stephen Rothwell wrote:
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/video/backlight/88pm860x_bl.c: In function 'pm860x_backlight_probe':
> drivers/video/backlight/88pm860x_bl.c:227: error: too few arguments to function 'backlight_device_register'
> drivers/video/backlight/max8925_bl.c: In function 'max8925_backlight_probe':
> drivers/video/backlight/max8925_bl.c:137: error: too few arguments to function 'backlight_device_register'
>
> Caused by commit 85d0968607ab8c61de45a68c643b198020a1369d ("backlight:
> Allow properties to be passed at registration") interacting with commits
> d07e8bf83fd71567aaf9c27c3b133ab3cf8f3c4c ("backlight: Enable backlight in
> 88pm860x") and 4f811ef0d40048ae80b6ea77080b814725bffc58 ("backlight:
> Enable max8925 backlight") which are now in Linus' tree (via the mfd tree)
Sorry about that, I knew there were going to be issues with that patch
and had meant to commit and test but not push until I fixed that issue.
I've fixed up the tree now.
Cheers,
Richard
next prev parent reply other threads:[~2010-03-11 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 7:03 linux-next: build failure after merge of the final tree (backlight related) Stephen Rothwell
2010-03-11 17:36 ` Richard Purdie [this message]
2010-03-12 9:54 ` Stephen Rothwell
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=1268328970.1625.2.camel@rex \
--to=rpurdie@rpsys.net \
--cc=haojian.zhuang@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=sameo@linux.intel.com \
--cc=sfr@canb.auug.org.au \
/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.