From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: how best to report results of my kernel tree scanning scripts?
Date: Sat, 26 Sep 2009 18:07:55 +0530 [thread overview]
Message-ID: <1253968675.4568.3.camel@ht.satnam> (raw)
In-Reply-To: <alpine.LFD.2.00.0909260811470.19017@localhost>
Hello Robert,
On Sat, 2009-09-26 at 08:16 -0400, Robert P. J. Day wrote:
> since the merge window appears to be ready to close fairly soon(?),
> i'm prepping to run my scanning scripts once again to identify (among
> other things):
>
> * unused Kconfig CONFIG variables
> * references to CONFIG_ variables that don't even exist (both in
> source files and Makefiles)
> * references to non-existent header files
>
> and bunches of other things. i'm open as to the best way to post the
> results, since different people have different opinions.
>
> and, no, i can't just submit patches since, in many cases, i have no
> idea what the fix should be (if any) -- that's the kind of decision
> best left to the respective subsystem maintainers.
>
> thoughts? this is where i put the old output:
>
> http://www.crashcourse.ca/wiki/index.php/Kernel_cleanup
>
Thanks for reporting these results, I will try to fix them and submit
patches with Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
Thanks,
--
JSR
next prev parent reply other threads:[~2009-09-26 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 12:16 how best to report results of my kernel tree scanning scripts? Robert P. J. Day
2009-09-26 12:37 ` Jaswinder Singh Rajput [this message]
2009-09-26 12:44 ` Robert P. J. Day
2009-09-27 6:41 ` Jaswinder Singh Rajput
2009-09-27 6:53 ` Jaswinder Singh Rajput
2009-11-08 19:52 ` Thiago Farina
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=1253968675.4568.3.camel@ht.satnam \
--to=jaswinder@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.