From: Boris Brezillon <boris.brezillon@free-electrons•com>
To: Mark Brown <broonie@kernel•org>
Cc: Nicolas Ferre <nicolas.ferre@microchip•com>,
kernel-build-reports@lists•linaro.org,
linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org,
linux-mtd@lists•infradead.org,
linux-arm-kernel@lists•infradead.org
Subject: Re: next-20170330 build: 2 failures 8 warnings (next-20170330)
Date: Thu, 30 Mar 2017 17:39:27 +0200 [thread overview]
Message-ID: <20170330173927.5665a0da@bbrezillon> (raw)
In-Reply-To: <20170330150742.wflswzqhg53mozx2@sirena.org.uk>
Hi Mark,
On Thu, 30 Mar 2017 16:07:42 +0100
Mark Brown <broonie@kernel•org> wrote:
> On Thu, Mar 30, 2017 at 01:50:39PM +0100, Build bot for Mark Brown wrote:
>
> Today's -next fails to build an ARM allmodconfig due to:
>
> > arm-allmodconfig
> > ../drivers/mtd/nand/atmel/nand-controller.c:2126:25: error: 'atmel_nc_id_table' undeclared here (not in a function)
> > ../include/linux/module.h:212:27: error: '__mod_of__atmel_nc_id_table_device_table' aliased to undefined symbol 'atmel_nc_id_table'
>
> caused by d09703f9459c94c78e029 (mtd: nand: Cleanup/rework the
> atmel_nand driver), it tries to export atmel_nc_id_table as the DT ID
> table but the variable is called atmel_nand_controller_of_ids.
Pushed a fixed version to nand/next.
Thanks for the report.
Boris
next prev parent reply other threads:[~2017-03-30 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 12:50 next-20170330 build: 2 failures 8 warnings (next-20170330) Build bot for Mark Brown
2017-03-30 14:57 ` Mark Brown
2017-03-30 15:07 ` Mark Brown
2017-03-30 15:39 ` Boris Brezillon [this message]
2017-03-30 16:09 ` Mark Brown
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=20170330173927.5665a0da@bbrezillon \
--to=boris.brezillon@free-electrons$(echo .)com \
--cc=broonie@kernel$(echo .)org \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-mtd@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=nicolas.ferre@microchip$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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