From: Randy Dunlap <randy.dunlap@oracle.com>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
akpm <akpm@linux-foundation.org>, Zhang Rui <rui.zhang@intel.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Zimny Lech <napohybelskurwysynom2010@gmail.com>
Subject: Re: on builds/randconfigs
Date: Wed, 12 Jan 2011 10:38:30 -0800 [thread overview]
Message-ID: <4D2DF526.7090308@oracle.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1101121257580.18873@x980>
On 01/12/11 10:35, Len Brown wrote:
>>> While I agree that randconfig build testing
>>> is theoretically useful, in recent memory
>>> its results do not seem particularly relevant
>>> to useful configs.
>>
>> Who defines useful?
>
> Simple.
>
> Configs that will be used are useful.
Then I suggest that you start deleting non-useful kernel configs.
You can begin in ACPI.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-01-12 18:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 5:36 linux-next: Tree for December 13 Stephen Rothwell
2010-12-13 19:20 ` [PATCH -next] thermal: depends on NET Randy Dunlap
2010-12-20 16:47 ` Randy Dunlap
2011-01-04 17:10 ` Randy Dunlap
2011-01-10 17:00 ` Randy Dunlap
2011-01-12 5:18 ` Len Brown
2011-01-12 17:48 ` on builds/randconfigs (was: [PATCH -next] thermal: depends on NET) Randy Dunlap
2011-01-12 18:35 ` Len Brown
2011-01-12 18:38 ` Randy Dunlap [this message]
2011-01-12 21:52 ` on builds/randconfigs Len Brown
2011-01-12 21:18 ` on builds/randconfigs (was: [PATCH -next] thermal: depends on NET) Andrew Morton
2011-01-12 21:24 ` Rafael J. Wysocki
2011-01-12 21:58 ` Len Brown
2011-01-12 22:15 ` Valdis.Kletnieks
2011-01-12 22:54 ` on builds/randconfigs Randy Dunlap
2011-01-13 0:44 ` on builds/randconfigs (was: [PATCH -next] thermal: depends on NET) Stephen Rothwell
2011-01-13 3:31 ` Len Brown
2011-01-13 3:45 ` Steven Rostedt
2011-01-13 3:48 ` Stephen Rothwell
2011-01-13 4:08 ` Linus Torvalds
2011-01-13 12:23 ` on builds/randconfigs Michal Marek
2011-01-15 12:24 ` Vegard Nossum
2011-01-15 16:09 ` Michal Marek
2010-12-13 19:44 ` [PATCH -next] cs5535: fix printk format warnings Randy Dunlap
2010-12-13 20:28 ` [PATCH V2 " Joe Perches
2010-12-13 20:42 ` Randy Dunlap
2010-12-13 20:57 ` [PATCH V3 " Joe Perches
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=4D2DF526.7090308@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=napohybelskurwysynom2010@gmail.com \
--cc=rui.zhang@intel.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).