Linux-Next discussions
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Build bot for Mark Brown <broonie@kernel.org>,
	kernel-build-reports@lists.linaro.org,
	linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
	heiko.carstens@de.ibm.com
Subject: Re: next-20170710 build: 2 failures 5 warnings (next-20170710)
Date: Mon, 10 Jul 2017 11:31:02 +0200	[thread overview]
Message-ID: <20170710093102.6mujx2p5od7gaa5k@piout.net> (raw)
In-Reply-To: <20170710192234.143c255f@canb.auug.org.au>

Hi,

On 10/07/2017 at 19:22:34 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> On Mon, 10 Jul 2017 08:47:12 +0100 Build bot for Mark Brown <broonie@kernel.org> wrote:
> >
> > ../include/linux/nvmem-provider.h:51:9: error: implicit declaration of function 'ERR_PTR' [-Werror=implicit-function-declaration]
> 
> Possibly caused by commit
> 
>   697e5a47aa12 ("rtc: add generic nvmem support")
> 
> from the rtc tree.  include/linux/nvmem-provider.h uses ERR_PTR, but
> does not include err.h :-(
> 

I'll fix it up. I was kind of relying on the kbuild test robot to catch
those. That code has been in a tree that they should be building for
more than two months but it seems to be timeouting a lot recently.


-- 
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2017-07-10  9:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10  7:47 next-20170710 build: 2 failures 5 warnings (next-20170710) Build bot for Mark Brown
2017-07-10  9:22 ` Stephen Rothwell
2017-07-10  9:31   ` Alexandre Belloni [this message]

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=20170710093102.6mujx2p5od7gaa5k@piout.net \
    --to=alexandre.belloni@free-electrons.com \
    --cc=broonie@kernel.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox