Re: any value in running my kernel scanning scripts before release?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 07/15/2010 01:32 PM, Robert P. J. Day wrote:
> 
>   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
> $

These are plain bugs, so it's IMO OK to send fixes for these at any time
before the final release. In the worst case, it will be merged after the
final release.

just my two cents,
Michal
--
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


[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux