From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Robert Jarzmik <robert.jarzmik@free.fr>,
Stefan Schmidt <stefan@openezx.org>,
openezx-devel@lists.openezx.org,
Daniel Ribeiro <drwyrm@gmail.com>,
linux-kernel@vger.kernel.org,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Thierry Reding <thierry.reding@gmail.com>,
Harald Welte <laforge@openezx.org>,
Daniel Mack <daniel@zonque.org>
Subject: Re: [PATCH] ARM: pxa: ezx: fix a910 camera data
Date: Fri, 25 Nov 2016 23:06:28 +0100 [thread overview]
Message-ID: <3367313.o4F01WBXRf@wuerfel> (raw)
In-Reply-To: <87inrbqr16.fsf@belgarion.home>
On Friday, November 25, 2016 8:48:53 PM CET Robert Jarzmik wrote:
> Arnd Bergmann <arnd@arndb.de> writes:
>
> > The camera_supply_dummy_device definition is shared between a780 and a910,
> > but only provided when the first is enabled and fails to build for a
> > configuration with only a910:
> >
> > arch/arm/mach-pxa/ezx.c:1097:3: error: 'camera_supply_dummy_device' undeclared here (not in a function)
> >
> > This moves the definition into its own section.
> >
> > Fixes: 6c1b417adc8f ("ARM: pxa: ezx: use the new pxa_camera platform_data")
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> Ah yes, I'll queue that up in pxa/fixes.
>
> This also means that you have a test robot which beats my Jenkins, as mine
> didn't complain. Do you have a specific defconfig or is it a randconfig which
> reveals that ?
>
It showed up in randconfig builds, two out of several hundred.
I'm not surprised that nobody else caught it.
Arnd
prev parent reply other threads:[~2016-11-25 22:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 16:29 [PATCH] ARM: pxa: ezx: fix a910 camera data Arnd Bergmann
2016-11-24 22:10 ` Stefan Schmidt
2016-11-25 19:53 ` Robert Jarzmik
2016-11-25 23:30 ` Stefan Schmidt
2016-12-03 16:55 ` Antonio Ospite
2016-12-03 18:49 ` Stefan Schmidt
2016-11-25 20:22 ` Harald Welte
2016-11-25 19:48 ` Robert Jarzmik
2016-11-25 22:06 ` 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=3367313.o4F01WBXRf@wuerfel \
--to=arnd@arndb.de \
--cc=daniel@zonque.org \
--cc=drwyrm@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=laforge@openezx.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openezx-devel@lists.openezx.org \
--cc=robert.jarzmik@free.fr \
--cc=stefan@openezx.org \
--cc=thierry.reding@gmail.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).