On Tue, Oct 29, 2013 at 06:29:59PM +0100, Laurent Pinchart wrote: > On Tuesday 29 October 2013 10:23:31 Mark Brown wrote: > > 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? > arch/cris for instance. We can use readl/writel instead (maybe it would be > time to rationalize and document the I/O accessors across all architectures, > but that's another topic). It'd certainly be sensible, or adding a config option to depend on if you rely on these functions. > My point is that there might be other issues that I won't be able to easily > catch. This would break compilation for everybody for no reason, as the > drivers are useless on non-SuperH, non-ARM platforms. That's why I believe > COMPILE_TEST would be a better option as a first step. Yes, it would - please do that. Note that it won't stop anyone running into build issues on other architectures though, it's just about stopping Kconfig noise.
signature.asc
Description: Digital signature
_______________________________________________ iommu mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/iommu
