From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/19] Enable various Renesas drivers on all ARM platforms
Date: Tue, 29 Oct 2013 14:22:28 +0100 [thread overview]
Message-ID: <1844190.ApyucSZX8W@avalon> (raw)
In-Reply-To: <1383051980.29619.33.camel@sauron.fi.intel.com>
Hi Artem,
On Tuesday 29 October 2013 15:06:20 Artem Bityutskiy wrote:
> On Tue, 2013-10-29 at 10:12 +0100, Guennadi Liakhovetski wrote:
> > 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.
The idea is that, if ARM is neither a compile-time nor runtime dependency, it
should not be specified in Kconfig. However, if the IP core has never been
used on anything but SuperH and ARM, I don't think clobbering the config
process with drivers that can't be used on the target architecture would be a
really good idea, especially now that we have a COMPILE_TEST Kconfig option.
My preference does goes to SUPERH || ARM || COMPILE_TEST over no dependency at
all.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-10-29 13:22 UTC|newest]
Thread overview: 46+ 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 01/19] serial: sh-sci: Enable the driver " Laurent Pinchart
2013-10-28 23:46 ` [PATCH 02/19] DMA: shdma: " Laurent Pinchart
2013-10-28 23:46 ` [PATCH 03/19] i2c: sh_mobile: " Laurent Pinchart
2013-10-29 5:03 ` Wolfram Sang
2013-10-29 9:43 ` Laurent Pinchart
2013-10-28 23:46 ` [PATCH 04/19] input: sh_keysc: " Laurent Pinchart
2013-10-28 23:46 ` [PATCH 05/19] iommu: shmobile: " Laurent Pinchart
2013-10-28 23:46 ` [PATCH 06/19] i2c: rcar: " Laurent Pinchart
2013-10-29 5:03 ` Wolfram Sang
2013-10-28 23:46 ` [PATCH 07/19] v4l: sh_vou: " Laurent Pinchart
2013-10-30 12:26 ` Mauro Carvalho Chehab
2013-11-06 0:57 ` Laurent Pinchart
2013-10-28 23:46 ` [PATCH 08/19] mmc: sdhi: " Laurent Pinchart
2013-10-29 9:07 ` Guennadi Liakhovetski
2013-10-29 9:52 ` Laurent Pinchart
2013-10-29 12:12 ` Sergei Shtylyov
2013-10-29 13:15 ` Laurent Pinchart
2013-10-29 20:47 ` Sergei Shtylyov
2013-10-29 22:23 ` Laurent Pinchart
2013-10-28 23:46 ` [PATCH 09/19] mmc: sh_mmcif: " Laurent Pinchart
2013-10-28 23:46 ` [PATCH 10/19] mtd: sh_flctl: " Laurent Pinchart
2013-10-28 23:46 ` [PATCH 11/19] net: sh_eth: Set receive alignment correctly " Laurent Pinchart
2013-10-28 23:47 ` [PATCH 12/19] irda: sh_irda: Enable the driver " Laurent Pinchart
2013-10-28 23:47 ` [PATCH 13/19] pinctrl: sh-pfc: " Laurent Pinchart
2013-10-28 23:47 ` [PATCH 14/19] pwm: pwm-renesas-tpu: " Laurent Pinchart
2013-10-28 23:47 ` [PATCH 15/19] sh: intc: " Laurent Pinchart
2013-10-28 23:47 ` [PATCH 16/19] spi: sh_msiof: " Laurent Pinchart
2013-10-29 16:40 ` Mark Brown
2013-10-28 23:47 ` [PATCH 17/19] spi: sh_hspi: " Laurent Pinchart
2013-10-28 23:47 ` [PATCH 18/19] thermal: rcar-thermal: " Laurent Pinchart
2013-10-28 23:47 ` [PATCH 19/19] fbdev: sh-mobile-lcdcfb: " 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
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 [this message]
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=1844190.ApyucSZX8W@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).