The main work of this driver is providing sys node for users to access data. Which directory will this driver be placed after moving from staging? It's better to rewrite it based on IIO. Otherwise, the architecture for this kind of driver will be difficult to be consistent. -barry On Mon, May 3, 2010 at 1:05 AM, Javier Martinez Canillas <martinez.javier@xxxxxxxxx> wrote: > > This patch solves a compilation error in today linux-next tree. > > The adis16255 staging driver Makefile seems to be wrong. I think this patch solves the issue. > > Signed-off-by: Javier Martinez Canillas <martinez.javier@xxxxxxxxx> > --- > drivers/staging/adis16255/Makefile | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/drivers/staging/adis16255/Makefile b/drivers/staging/adis16255/Makefile > index 3f8b1f0..dc4debc 100644 > --- a/drivers/staging/adis16255/Makefile > +++ b/drivers/staging/adis16255/Makefile > @@ -1 +1 @@ > -obj-$(CONFIG_ADIS16255) +�is16255.o > +obj-$(CONFIG_ADIS16255) += adis1625.o > -- > 1.7.0.4 > > > > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
