normally i wait for the merge window, then run my kernel scanning
scripts and post results. any interest in me doing that earlier? i
just did a quick test and found a number of incongruities like, for
example:
$ grep -r "config QT2160" *
drivers/input/keyboard/Kconfig:config QT2160
$
$ grep -r KEYBOARD_QT2160 *
drivers/input/keyboard/Makefile:obj-$(CONFIG_KEYBOARD_QT2160) += qt2160.o
$
which is a fairly obvious mismatch between the config variable and
the test, yes?
anyway, i'm open to suggestions.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Top-notch, inexpensive online Linux/OSS/kernel courses
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-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
