public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: kernel-build-reports@lists.linaro.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Build bot for Mark Brown <broonie@kernel.org>,
	Stephen Warren <swarren@nvidia.com>,
	Colin Cross <ccross@android.com>, Olof Johansson <olof@lixom.net>,
	Thierry Reding <treding@nvidia.com>,
	linaro-kernel@lists.linaro.org, Mirza Krak <mirza.krak@gmail.com>,
	Marcel Ziswiler <marcel.ziswiler@toradex.com>,
	Jon Hunter <jonathanh@nvidia.com>,
	linux-next@vger.kernel.org
Subject: Re: next-20161108 build: 2 failures 1 warnings (next-20161108)
Date: Tue, 08 Nov 2016 15:56:23 +0100	[thread overview]
Message-ID: <1939700.Y8FDAGyee3@wuerfel> (raw)
In-Reply-To: <20161108225858.17b3440d@canb.auug.org.au>

On Tuesday, November 8, 2016 10:58:58 PM CET Stephen Rothwell wrote:
> Hi all,
> 
> On Tue, 08 Nov 2016 10:39:01 +0000 Build bot for Mark Brown <broonie@kernel.org> wrote:
> >
> >       arm64-allmodconfig
> > ../drivers/bus/tegra-gmi.c:97:11: error: 'dev' undeclared (first use in this function)
> > 
> >       arm-allmodconfig
> > ../drivers/bus/tegra-gmi.c:97:11: error: 'dev' undeclared (first use in this function)
> 
> Caused by commit
> 
>   4f95e6a5c9e4 ("bus: Add support for Tegra Generic Memory Interface")
> 
> from the tegra tree.
> 

Sent a fix now, along with 22 more patches for new warnings and build errrors
in linux-next.

	Arnd

      reply	other threads:[~2016-11-08 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08 10:39 next-20161108 build: 2 failures 1 warnings (next-20161108) Build bot for Mark Brown
2016-11-08 11:58 ` Stephen Rothwell
2016-11-08 14:56   ` Arnd Bergmann [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=1939700.Y8FDAGyee3@wuerfel \
    --to=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=ccross@android.com \
    --cc=jonathanh@nvidia.com \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-next@vger.kernel.org \
    --cc=marcel.ziswiler@toradex.com \
    --cc=mirza.krak@gmail.com \
    --cc=olof@lixom.net \
    --cc=sfr@canb.auug.org.au \
    --cc=swarren@nvidia.com \
    --cc=treding@nvidia.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