On 10/07/13 15:35, Marek Vasut wrote: > Dear Lars-Peter Clausen, > >> On 10/07/2013 03:26 PM, Lars-Peter Clausen wrote: >>> None of the SPEAr, LPC32XX or MXS ADC drivers have a compile time >>> dependency on their respective platform. So make it possible to build >>> the drivers when CONFIG_COMPILE_TEST is set. This makes it easier to >>> compile test changes. >>> I'm getting a ERROR: "stmp_reset_block" [drivers/staging/iio/adc/mxs-lradc.ko] undefined! Also for reference also the following warnings from a build with sparse enabled. CHECK drivers/staging/iio/adc/mxs-lradc.c drivers/staging/iio/adc/mxs-lradc.c:1298:25: warning: incorrect type in argument 1 (different address spaces) drivers/staging/iio/adc/mxs-lradc.c:1298:25: expected void const *ptr drivers/staging/iio/adc/mxs-lradc.c:1298:25: got void [noderef] <asn:2>*base drivers/staging/iio/adc/mxs-lradc.c:1299:37: warning: incorrect type in argument 1 (different address spaces) drivers/staging/iio/adc/mxs-lradc.c:1299:37: expected void const *ptr drivers/staging/iio/adc/mxs-lradc.c:1299:37: got void [noderef] <asn:2>*base CC [M] drivers/staging/iio/adc/mxs-lradc.o CHECK drivers/staging/iio/adc/spear_adc.c drivers/staging/iio/adc/spear_adc.c:321:18: warning: cast removes address space of expression drivers/staging/iio/adc/spear_adc.c:320:33: warning: incorrect type in assignment (different address spaces) drivers/staging/iio/adc/spear_adc.c:320:33: expected struct adc_regs_spear3xx [noderef] <asn:2>*adc_base_spear3xx drivers/staging/iio/adc/spear_adc.c:320:33: got struct adc_regs_spear3xx *<noident> I haven't even glanced at what caused these as yet. >>> Signed-off-by: Lars-Peter Clausen <lars@xxxxxxxxxx> >>> Cc: Stefan Roese <sr@xxxxxxx> >>> Cc: Marek Vasut <marex@xxxxxxx >> >> Missing > here, added Marek to Cc manually > > Thanks. Makes sense to me > > Reviewed-by: Marek Vasut <marex@xxxxxxx> > > Best regards, > Marek Vasut > -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html