Hi Can some one help me to answer these question?
drivers/staging/asus_oled/TODO:
- checkpatch.pl cleanups
CHECK nothing to do (DONE):
./scripts/checkpatch.pl --terse --file drivers/staging/asus_oled/asus_oled.c
- sparse fixes
What's that???
- audit the userspace interface
Who should do this? The user interface is with sysfs clearly explain
in the README (/sys/class/asus_oled/oled_N).
- sysfs vs. char?
Who should decide? If we need to switch it to char I'm willing to do it.
- Documentation/ABI/ needs to be added
and formating it to fit with ABI... If I understand correctly we
should grab the information from README and format it properly to be
inserted into Documentation/ABI/testing/sysfs-class-asus_oled???
- put the sample .txt files and README file somewhere.
in ABI documentation and keeping one tux.txt example
Jakub Any suggestion on which to keep?
Best Regards
Kevyn-Alexandre Pare
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
