On Thu, Jun 12, 2014 at 04:15:32PM +0200, Arnd Bergmann wrote: > On Thursday 12 June 2014 16:12:17 Laurent Pinchart wrote: > > > From 3a965f4fd5a6b3ef4a66aa4e7c916cfd34fd5706 Mon Sep 17 00:00:00 2001 > > > From: Arnd Bergmann <arnd@xxxxxxxx> > > > Date: Tue, 21 Jan 2014 09:32:43 +0100 > > > Subject: [PATCH] [media] staging: tighten omap4iss dependencies > > > > > > The OMAP4 camera support depends on I2C and VIDEO_V4L2, both > > > of which can be loadable modules. This causes build failures > > > if we want the camera driver to be built-in. > > > > > > This can be solved by turning the option into "tristate", > > > which unfortunately causes another problem, because the > > > driver incorrectly calls a platform-internal interface > > > for omap4_ctrl_pad_readl/omap4_ctrl_pad_writel. > > > > > > Instead, this patch just forbids the invalid configurations > > > and ensures that the driver can only be built if all its > > > dependencies are built-in. > > > > > > Signed-off-by: Arnd Bergmann <arnd@xxxxxxxx> > > > > Acked-by: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx> > > > > Should I take this in my tree for v3.17 or would you like to fast-track it ? > > > > I'd actually like to see it in 3.15 as a stable backport if possible, It's not stable material, sorry. > but definitely in 3.16. What is the normal path for staging/media > but fix patches? Through Mauro's tree. greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
