From: Samuel Ortiz <sameo@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: linux-next: build failure after merge of the final tree (mfd tree related)
Date: Mon, 20 Dec 2010 11:33:37 +0100 [thread overview]
Message-ID: <20101220103336.GC11095@sortiz-mobl> (raw)
In-Reply-To: <20101220192121.47767525.sfr@canb.auug.org.au>
Hi Stephen,
On Mon, Dec 20, 2010 at 07:21:21PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
Ok, I removed Mark's commit, the MFD tree should build fine now.
I'm keeping this one for whenever we'll have a proper pwm framework.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2010-12-20 10:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 8:21 linux-next: build failure after merge of the final tree (mfd tree related) Stephen Rothwell
2010-12-20 10:33 ` Samuel Ortiz [this message]
2010-12-20 10:52 ` Mark Brown
2010-12-20 12:18 ` Mark Brown
2010-12-20 12:28 ` [PATCH] misc: Make AB8500_PWM driver depend on U8500 due to PWM breakage Mark Brown
2010-12-20 13:00 ` Samuel Ortiz
-- strict thread matches above, loose matches on Subject: below --
2013-06-18 7:19 linux-next: build failure after merge of the final tree (mfd tree related) Stephen Rothwell
2013-06-19 8:24 ` Samuel Ortiz
2013-06-20 2:25 ` Chao Xie
2012-09-17 11:38 Stephen Rothwell
2012-09-17 13:28 ` Samuel Ortiz
2011-12-21 6:33 Stephen Rothwell
2011-12-21 10:51 ` Cousson, Benoit
2011-12-21 10:51 ` Cousson, Benoit
2011-12-21 12:24 ` Samuel Ortiz
2011-12-22 17:30 ` Samuel Ortiz
2011-03-28 3:52 Stephen Rothwell
2011-03-21 8:12 함명주
2011-03-21 8:12 ` 함명주
2011-03-21 2:59 Stephen Rothwell
2010-09-14 3:43 Stephen Rothwell
2010-09-14 5:05 ` Arun MURTHY
2010-09-16 7:15 ` Arun MURTHY
2010-09-16 7:23 ` Stephen Rothwell
2010-09-16 8:51 ` 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=20101220103336.GC11095@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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.