On Fri, Oct 07, 2016 at 06:15:44PM +0300, Pantelis Antoniou wrote: > Introduce a staging driver containing all the bit and > pieces of Juniper's board support infrastructure that don't quite > fit in any other place. Why staging? > The Juniper series of routers comprise of both x86 and powerpc > platforms that contain similar hardware components necessitating > common support methods. > > Note that this is the first submission and we expect things to be > moved around as required. > > This patchset is against mainline as of today: v4.8-9431-g3477d16 > and is dependent on the "Juniper prerequisites" patchset sent > earlier. sent where? Why not just make a single patch series? > Rajat Jain (1): > jnx: Introduce include/linux/jnx/pci_ids.h > > Tom Kavanagh (1): > staging: jnx: Juniper subsystem & board core APIs > > Documentation/ABI/testing/sysfs-platform-jnx | 170 +++++++ > drivers/staging/Kconfig | 2 + > drivers/staging/Makefile | 1 + > drivers/staging/jnx/Kconfig | 24 + > drivers/staging/jnx/Makefile | 5 + > drivers/staging/jnx/jnx-board-core.c | 247 ++++++++++ > drivers/staging/jnx/jnx-subsys-private.h | 35 ++ > drivers/staging/jnx/jnx-subsys.c | 655 +++++++++++++++++++++++++++ > include/linux/jnx/jnx-board-core.h | 41 ++ > include/linux/jnx/jnx-subsys.h | 94 ++++ > include/linux/jnx/pci_ids.h | 66 +++ staging drivers have to be self-contained, no files outside of your subdirectory please. Once they have "passed" proper review, then you can move files out. Also, I need a TODO file listing what needs to be done, who to contact, and other info about the code. And again, why not just submit this to the real part of the kernel? thanks, greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
