forked from Minki/linux
staging: dgrp: add dgrp to the build
Kconfig and Makefile changes to add dgrp to the build system. Signed-off-by: Bill Pemberton <wfp5p@virginia.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
parent
0b52b74972
commit
7b6d45c211
@ -136,4 +136,6 @@ source "drivers/staging/csr/Kconfig"
|
||||
|
||||
source "drivers/staging/omap-thermal/Kconfig"
|
||||
|
||||
source "drivers/staging/dgrp/Kconfig"
|
||||
|
||||
endif # STAGING
|
||||
|
@ -60,3 +60,4 @@ obj-$(CONFIG_USB_G_CCG) += ccg/
|
||||
obj-$(CONFIG_WIMAX_GDM72XX) += gdm72xx/
|
||||
obj-$(CONFIG_CSR_WIFI) += csr/
|
||||
obj-$(CONFIG_OMAP_BANDGAP) += omap-thermal/
|
||||
obj-$(CONFIG_DGRP) += dgrp/
|
||||
|
@ -1,7 +1,13 @@
|
||||
- Use configfs for config stuff. This will require changes to the
|
||||
user space code.
|
||||
|
||||
- Check the calls to tty_register_device. In particular, check to see
|
||||
if there should be some handling for IS_ERR(classp).
|
||||
|
||||
- dgrp_send() and dgrp_receive() could use some refactoring
|
||||
|
||||
- Don't automatically create CHAN_MAX (64) channel array entries for
|
||||
every device as many devices are going to have much less than 64
|
||||
channels.
|
||||
|
||||
- The locking needs to be checked. It seems haphazardly done in most
|
||||
places.
|
||||
|
||||
- Check Kconfig dependencies
|
||||
|
Loading…
Reference in New Issue
Block a user