linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-fbdev@vger.kernel.org, linux-sh@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-mtd@lists.infradead.org, linux-i2c@vger.kernel.org,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	Vinod Koul <vinod.koul@intel.com>, Joerg Roedel <joro@8bytes.org>,
	Wolfram Sang <wsa@the-dreams.de>,
	Magnus Damm <magnus.damm@gmail.com>,
	Eduardo Valentin <eduardo.valentin@ti.com>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	linux-serial@vger.kernel.org, linux-input@vger.kernel.org,
	Zhang Rui <rui.zhang@intel.com>, Chris Ball <cjb@laptop.org>,
	Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
	linux-media@vger.kernel.org, linux-pwm@vger.kernel.org,
	Samuel Ortiz <samuel@sortiz.org>,
	linux-pm@vger.kernel.org,
	Ian Molton <ian@mnementh.co.uk>Mark Brown <b>
Subject: Re: [PATCH 00/19] Enable various Renesas drivers on all ARM platforms
Date: Tue, 29 Oct 2013 15:06:20 +0200	[thread overview]
Message-ID: <1383051980.29619.33.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1310291009121.8404@axis700.grange>

On Tue, 2013-10-29 at 10:12 +0100, Guennadi Liakhovetski wrote:
> Hi Laurent
> 
> On Tue, 29 Oct 2013, Laurent Pinchart wrote:
> 
> > Hello,
> > 
> > This patch series, based on v3.12-rc7, prepares various Renesas drivers
> > for migration to multiplatform kernels by enabling their compilation or
> > otherwise fixing them on all ARM platforms. The patches are pretty
> > straightforward and are described in their commit message.
> > 
> > I'd like to get all these patches merged in v3.14. As they will need to go
> > through their respective subsystems' trees, I would appreciate if all
> > maintainers involved could notify me when they merge patches from this series
> > in their tree to help me tracking the merge status. I don't plan to send pull
> > requests individually for these patches, and I will repost patches
> > individually if changes are requested during review.
> > 
> > If you believe the issue should be solved in a different way (for instance by
> > removing the architecture dependency completely) please reply to the cover
> > letter to let other maintainers chime in.
> 
> Exactly this was my doubt. If we let these drivers build on all ARM 
> platforms... Maybe we should just let them build everywhere? Unless there 
> are real ARM dependencies. Maybe you could try to remove the restriction 
> and try to build them all on x86?

If they have never been used on anything but ARM, why would you remove
ARM dependencies? Just for the sake of compile-checking?

Also, if ARM dependency is ever removed, all these should become 'n' by
default in the Kconfig, in order to make sure they do not slip into
defconfigs of different architectures.

-- 
Best Regards,
Artem Bityutskiy

  parent reply	other threads:[~2013-10-29 13:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 23:46 [PATCH 00/19] Enable various Renesas drivers on all ARM platforms Laurent Pinchart
2013-10-28 23:46 ` [PATCH 04/19] input: sh_keysc: Enable the driver " Laurent Pinchart
2013-10-29  6:04 ` [PATCH 00/19] Enable various Renesas drivers " Simon Horman
2013-10-29 16:04   ` Mark Brown
     [not found]     ` <20131029160449.GD16686-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-10-29 17:05       ` Laurent Pinchart
2013-10-29 17:23         ` Mark Brown
     [not found]           ` <20131029172331.GA20251-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-10-29 17:29             ` Laurent Pinchart
2013-10-29 17:58               ` Mark Brown
2013-10-30  0:05                 ` Simon Horman
2013-10-30 10:59                   ` Tomi Valkeinen
2013-10-29  9:12 ` Guennadi Liakhovetski
     [not found]   ` <Pine.LNX.4.64.1310291009121.8404-0199iw4Nj15frtckUFj5Ag@public.gmane.org>
2013-10-29  9:46     ` Laurent Pinchart
2013-10-29 13:06   ` Artem Bityutskiy [this message]
     [not found]     ` <1383051980.29619.33.camel-Bxnoe/o8FG+Ef9UqXRslZEEOCMrvLtNR@public.gmane.org>
2013-10-29 13:22       ` Laurent Pinchart
2013-10-29 13:54         ` Artem Bityutskiy
2013-10-29 16:28 ` Linus Walleij

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=1383051980.29619.33.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=cjb@laptop.org \
    --cc=eduardo.valentin@ti.com \
    --cc=g.liakhovetski+renesas@gmail.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=ian@mnementh.co.uk \
    --cc=joro@8bytes.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=plagnioj@jcrosoft.com \
    --cc=rui.zhang@intel.com \
    --cc=samuel@sortiz.org \
    --cc=thierry.reding@gmail.com \
    --cc=tomi.valkeinen@ti.com \
    --cc=vinod.koul@intel.com \
    --cc=wsa@the-dreams.de \
    /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).