2011/3/23 Greg KH <gregkh@xxxxxxx>: >> arch/arm/mach-ux500/Makefile | 4 + >> arch/arm/mach-ux500/board-mop500.c | 160 ++++++++++++++++ >> arch/arm/mach-ux500/devices-cg2900.c | 349 ++++++++++++++++++++++++++++++++++ >> arch/arm/mach-ux500/devices-cg2900.h | 19 ++ >> 4 files changed, 532 insertions(+), 0 deletions(-) >> create mode 100644 arch/arm/mach-ux500/devices-cg2900.c >> create mode 100644 arch/arm/mach-ux500/devices-cg2900.h > > As this touches ARM specific code, I need an ack from the ARM maintainer > before I can take this through the staging tree. Is there any way to > make it part of your drivers/staging/ submission? There are other > examples in the staging tree already that do this, why not do that here > as well? Hm yeah maybe it's possible if you move devices-cg2900.* to staging/cg2900, then split off the stuff in board-mop500.c into some drivers/staging/cg2900/board-mop500-cg2900.c which adds the device in some proper initcall. Do you think it can be done P-G? I might have overestimated the work involved in moving that stuff to /staging. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
