From: Michal Marek <mmarek@suse.cz>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-input@vger.kernel.org
Subject: Re: any value in running my kernel scanning scripts before release?
Date: Thu, 15 Jul 2010 15:28:59 +0200 [thread overview]
Message-ID: <4C3F0D1B.9060403@suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.00.1007150728520.13042@lynx>
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
next prev parent reply other threads:[~2010-07-15 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 11:32 any value in running my kernel scanning scripts before release? Robert P. J. Day
2010-07-15 13:28 ` Michal Marek [this message]
2010-07-15 22:50 ` Robert P. J. Day
2010-07-16 3:00 ` Greg KH
2010-07-16 8:27 ` Robert P. J. Day
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C3F0D1B.9060403@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox