just noticed that, in linux-next (but not linus' tree), all of
drivers/message/i2o/ was moved to staging:
+ drivers/{message => staging}/i2o/Kconfig | 1 -
+ drivers/{message => staging}/i2o/Makefile | 0
+ drivers/{message => staging}/i2o/README | 0
+ drivers/{message => staging}/i2o/README.ioctl | 0
+ drivers/{message => staging}/i2o/bus-osm.c | 2 +-
+ drivers/{message => staging}/i2o/config-osm.c | 2 +-
+ drivers/{message => staging}/i2o/core.h | 0
+ drivers/{message => staging}/i2o/debug.c | 2 +-
+ drivers/{message => staging}/i2o/device.c | 2 +-
+ drivers/{message => staging}/i2o/driver.c | 2 +-
+ drivers/{message => staging}/i2o/exec-osm.c | 2 +-
+ {include/linux => drivers/staging/i2o}/i2o.h | 0
+ drivers/{message => staging}/i2o/i2o_block.c | 2 +-
+ drivers/{message => staging}/i2o/i2o_block.h | 0
+ drivers/{message => staging}/i2o/i2o_config.c | 0
+ drivers/{message => staging}/i2o/i2o_proc.c | 2 +-
+ drivers/{message => staging}/i2o/i2o_scsi.c | 2 +-
+ drivers/{message => staging}/i2o/iop.c | 2 +-
+ drivers/{message => staging}/i2o/memory.c | 2 +-
+ drivers/{message => staging}/i2o/pci.c | 2 +-
which immediately breaks the generation of device-drivers.html in
linux-next:
DOCPROC Documentation/DocBook/device-drivers.xml
docproc: .//include/linux/i2o.h: No such file or directory
Documentation/DocBook/Makefile:93: recipe for target 'Documentation/DocBook/device-drivers.xml' failed
make[1]: *** [Documentation/DocBook/device-drivers.xml] Error 1
Makefile:1380: recipe for target 'htmldocs' failed
make: *** [htmldocs] Error 2
should .tmpl files ever refer to content under drivers/staging? or
should that inclusion just be removed from device-drivers.tmpl?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
