From: Mark Brown <broonie@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Simon Horman <horms@verge.net.au>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
linux-sh@vger.kernel.org, linux-fbdev@vger.kernel.org,
Wolfram Sang <wsa@the-dreams.de>,
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,
Vinod Koul <vinod.koul@intel.com>, Joerg Roedel <joro@8bytes.org>,
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>,
linux-arm-kernel@lists.infradead.org,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org, iommu@lists.linux-foundation.org,
netdev@vger.kernel.org, dmaengine@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
"David S. Miller" <davem@davemloft.net>,
Mauro Carvalho Chehab <m.chehab@samsung.com>
Subject: Re: [PATCH 00/19] Enable various Renesas drivers on all ARM platforms
Date: Tue, 29 Oct 2013 10:23:31 -0700 [thread overview]
Message-ID: <20131029172331.GA20251@sirena.org.uk> (raw)
In-Reply-To: <1577821.Q7gttkPE2J@avalon>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
On Tue, Oct 29, 2013 at 06:05:53PM +0100, Laurent Pinchart wrote:
> The first one is that I can't compile-test all those drivers on all
> architectures. The spi-sh-msiof driver, for instance, uses io(read|write)(16|
Which architectures are these and is there not a symbol we can depend on
for them?
> 32) which are not available on all architectures. There might be other similar
> problems that I can't catch, and I don't want to introduce build breakages in
> the kernel.
This is easy enough to handle if we do run into issues, it seems better
to get things available than try to step through architecture by
architecture.
> The second reason is that, as the IP cores have never been used on anything
> but SuperH and ARM, I don't like the idea of clobbering the config process
> with drivers that are useless on the target architecture. Now that we have a
> COMPILE_TEST Kconfig option, my preference would thus go to SUPERH || ARM ||
> COMPILE_TEST over no dependency at all.
That's not what you did, though - you're not adding COMPILE_TEST.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-10-29 17:23 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:47 ` [PATCH 14/19] pwm: pwm-renesas-tpu: 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
2013-10-29 17:05 ` Laurent Pinchart
2013-10-29 17:23 ` Mark Brown [this message]
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
2013-10-29 9:46 ` Laurent Pinchart
2013-10-29 13:06 ` Artem Bityutskiy
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=20131029172331.GA20251@sirena.org.uk \
--to=broonie@kernel.org \
--cc=cjb@laptop.org \
--cc=davem@davemloft.net \
--cc=dmaengine@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=eduardo.valentin@ti.com \
--cc=g.liakhovetski+renesas@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms@verge.net.au \
--cc=ian@mnementh.co.uk \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mmc@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=linux-spi@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=rui.zhang@intel.com \
--cc=samuel@sortiz.org \
--cc=sergei.shtylyov@cogentembedded.com \
--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