linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: Arnd Bergmann <arnd@arndb.de>, Robert Jarzmik <robert.jarzmik@free.fr>
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"
	<openezx-devel@lists.openezx.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: pxa: ezx: fix a910 camera data
Date: Thu, 24 Nov 2016 23:10:09 +0100	[thread overview]
Message-ID: <e0bdf159-93f2-5ed7-1e28-7fb80707d6c7@datenfreihafen.org> (raw)
In-Reply-To: <20161124162955.3887066-1-arnd@arndb.de>

Hello.

On 24.11.2016 17:29, Arnd Bergmann wrote:
> 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>
> ---
>  arch/arm/mach-pxa/ezx.c | 56 ++++++++++++++++++++++++++-----------------------

I wonder what we should do with ezx.c.

As far as I know neither Daniel nor Harald or myself are doing anything
with this devices anymore. Besides a basic compile test having an ack or
reviewed by from our side is a bit worthless. :/

I should still have some of these phones around in a box somewhere. If
there is someone with a good motivation and time to take over on this
platform we will find a way to get the person this devices.

Any takers? Robert? I guess you are already overloaded but you might
also have an interest. Worth asking :)

In the case nobody wants to pick up here what would you consider the
bets way forward? I could send a patch removing ezx platform support
from the kernel (basically ezx.c plus build support) or I can send a
patch marking it at least orphan in MAINTAINERS. Let me know what you think.

Daniel, Harald, if one of you is still interested in these and what to
pick up the work again, please speak up now. :)

regards
Stefan Schmidt

  reply	other threads:[~2016-11-24 22:19 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 [this message]
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

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=e0bdf159-93f2-5ed7-1e28-7fb80707d6c7@datenfreihafen.org \
    --to=stefan@datenfreihafen.org \
    --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=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).