linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Daniel Ribeiro <drwyrm@gmail.com>,
	Stefan Schmidt <stefan@openezx.org>,
	Harald Welte <laforge@openezx.org>,
	Daniel Mack <daniel@zonque.org>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	openezx-devel@lists.openezx.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: pxa: ezx: fix a910 camera data
Date: Fri, 25 Nov 2016 20:48:53 +0100	[thread overview]
Message-ID: <87inrbqr16.fsf@belgarion.home> (raw)
In-Reply-To: <20161124162955.3887066-1-arnd@arndb.de> (Arnd Bergmann's message of "Thu, 24 Nov 2016 17:29:18 +0100")

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 ?

Cheers.

--
Robert

  parent reply	other threads:[~2016-11-25 19:49 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 [this message]
2016-11-25 22:06   ` Arnd Bergmann

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=87inrbqr16.fsf@belgarion.home \
    --to=robert.jarzmik@free.fr \
    --cc=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=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).