linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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,
	Chao Xie <chao.xie@marvell.com>, Yi Zhang <yizhang@marvell.com>
Subject: Re: linux-next: build failure after merge of the final tree (mfd tree related)
Date: Wed, 19 Jun 2013 10:24:57 +0200	[thread overview]
Message-ID: <20130619082456.GR7161@zurbaran> (raw)
In-Reply-To: <20130618171957.9d8fbcf376243d1d5f1d92b0@canb.auug.org.au>

Hi Stephen,

On Tue, Jun 18, 2013 at 05:19:57PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
> 
> drivers/mfd/88pm800.c: In function 'pm800_pages_init':
> drivers/mfd/88pm800.c:434:2: error: implicit declaration of function 'IS_ERR' [-Werror=implicit-function-declaration]
>   if (IS_ERR(subchip->regmap_power)) {
>   ^
> drivers/mfd/88pm800.c:435:3: error: implicit declaration of function 'PTR_ERR' [-Werror=implicit-function-declaration]
>    ret = PTR_ERR(subchip->regmap_power);
>    ^
> 
> Caused by commit f8ca616f67f7 ("mfd: 88pm800: Enhance error handling for
> sub pages probe/remove") from the mfd tree.  Forgot to include
> linux/err.h (see Rule 1 in Documentation/SubmitChecklist).
Sorry about that. This is fixed now.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  reply	other threads:[~2013-06-19  8:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2013-06-20  2:25   ` Chao Xie
  -- strict thread matches above, loose matches on Subject: below --
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 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  2:59 Stephen Rothwell
2010-12-20  8:21 Stephen Rothwell
2010-12-20 10:33 ` Samuel Ortiz
2010-12-20 10:52   ` Mark Brown
2010-12-20 12:18     ` Mark Brown
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=20130619082456.GR7161@zurbaran \
    --to=sameo@linux.intel.com \
    --cc=chao.xie@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=yizhang@marvell.com \
    /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;
as well as URLs for NNTP newsgroup(s).