From: "Martin J. Bligh" <mbligh@mbligh.org>
To: paolo.ciarrocchi@gmail.com, nish.aravamudan@gmail.com
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-mm3
Date: Mon, 12 Sep 2005 15:50:51 -0700 [thread overview]
Message-ID: <212680000.1126565451@flay> (raw)
In-Reply-To: <4d8e3fd3050912140439c14518@mail.gmail.com>
--On Monday, September 12, 2005 23:04:47 +0200 Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com> wrote:
> On 9/12/05, Nish Aravamudan <nish.aravamudan@gmail.com> wrote:
>> On 9/12/05, Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com> wrote:
>> > On 9/12/05, Andrew Morton <akpm@osdl.org> wrote:
> [...]
>> > >
>> > > - There are several performance tuning patches here which need careful
>> > > attention and testing. (Does anyone do performance testing any more?)
>> >
>> > How about the tool announced months ago by Martin J. Bligh ?
>> >
>> > http://ftp.kernel.org/pub/linux/kernel/people/mbligh/abat/regression_matrix.html
>>
>> Preferred location is: test.kernel.org (much shorter too!)
>
> I wasn't aware of that, thank you! Now I won't forget anymore that URL ;-)
>
>> Also, the problem for -mm3 is that -mm2 did not build on most
>> machines. -mm1 did on 4/6. Probably some determination could be made
>> from those.
>
> I see. But I still think that automated testing is a great opportunity
> for the community to pinpoint problems.
>
> Is there anything we can do to make thinks work better ?
Stop breaking kernels from compiling? ;-) If people tested their patches
before fixing them, would make it easier ...
Or as Nish suggested, fixing some of them helps. it's exhausting to try
to debug all of them myself. Yes, I'm aware that some require specific
hardware access, and are a pain in the butt ...
I can very easily test fixes that are sent to me as a straight patch
URL on top of the kernel in question, anything else is a hassle (hint:
this ain't a full-time job for me ;-))
M.
next prev parent reply other threads:[~2005-09-12 22:50 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 9:43 2.6.13-mm3 Andrew Morton
2005-09-12 11:47 ` 2.6.13-mm3 Michal Piotrowski
2005-09-12 11:48 ` 2.6.13-mm3 [OOPS] vfs, page_owner, full reproductively, badness in vsnprintf Michal Piotrowski
2005-09-12 17:54 ` Alexander Nyberg
2005-09-12 18:48 ` Ingo Oeser
2005-09-12 21:13 ` Michal Piotrowski
2005-09-12 22:44 ` Andrew Morton
2005-09-12 22:56 ` Michal Piotrowski
2005-09-12 23:16 ` Andrew Morton
2005-09-12 13:15 ` 2.6.13-mm3 Reuben Farrelly
2005-09-12 14:17 ` 2.6.13-mm3 BUG in ntfs or slab Jiri Slaby
2005-09-12 14:21 ` Jiri Slaby
2005-09-12 14:45 ` Anton Altaparmakov
2005-09-12 14:17 ` 2.6.13-mm3 Andrew Walrond
2005-09-12 14:26 ` 2.6.13-mm3 Nick Piggin
2005-09-12 14:54 ` 2.6.13-mm3 Sonny Rao
2005-09-12 19:56 ` 2.6.13-mm3 Andrew Morton
2005-09-12 20:09 ` 2.6.13-mm3 Sonny Rao
2005-09-12 20:55 ` 2.6.13-mm3 Andrew Morton
2005-09-12 21:03 ` 2.6.13-mm3 Danny ter Haar
2005-09-12 22:06 ` 2.6.13-mm3 Sonny Rao
2005-09-12 22:47 ` 2.6.13-mm3 Martin J. Bligh
2005-09-13 5:19 ` 2.6.13-mm3 Danny ter Haar
2005-09-13 6:35 ` 2.6.13-mm3 Sonny Rao
2005-09-13 5:14 ` 2.6.13-mm3 Danny ter Haar
2005-09-13 7:02 ` 2.6.13-mm3 Sonny Rao
2005-09-13 14:31 ` 2.6.13-mm3 Martin J. Bligh
2005-09-13 18:32 ` 2.6.13-mm3 Sonny Rao
2005-09-13 18:46 ` 2.6.13-mm3 Sonny Rao
2005-09-12 15:19 ` 2.6.13-mm3 Paolo Ciarrocchi
2005-09-12 20:13 ` 2.6.13-mm3 Nish Aravamudan
2005-09-12 21:04 ` 2.6.13-mm3 Paolo Ciarrocchi
2005-09-12 21:07 ` 2.6.13-mm3 Nish Aravamudan
2005-09-12 22:50 ` Martin J. Bligh [this message]
2005-09-12 19:40 ` 2.6.13-mm3 Sonny Rao
[not found] ` <200509122106.j8CL6WPk006092@wscnet.wsc.cz>
2005-09-12 21:49 ` 2.6.13-mm3 Sonny Rao
2005-09-12 22:10 ` 2.6.13-mm3 Sonny Rao
2005-09-13 0:51 ` 2.6.13-mm3 Jiri Slaby
2005-09-13 5:58 ` 2.6.13-mm3 Sonny Rao
[not found] ` <20050912222437.GA13124@sergelap.austin.ibm.com>
2005-09-12 23:10 ` ibmvscsi badness (Re: 2.6.13-mm3) Andrew Morton
2005-09-13 1:38 ` Anton Blanchard
2005-09-13 8:56 ` serue
2005-09-13 15:09 ` [Patch] ibmvscsi compatibility fix Dave C Boutcher
2005-09-13 15:18 ` James Bottomley
2005-09-13 18:10 ` Serge E. Hallyn
2005-09-13 19:16 ` Serge E. Hallyn
2005-09-13 4:04 ` ibmvscsi badness (Re: 2.6.13-mm3) Anton Blanchard
2005-09-13 5:10 ` Dave C Boutcher
2005-09-18 0:38 ` Benjamin Herrenschmidt
2005-09-13 0:02 ` drivers/usb/class/bluetty.c does NOT build Lion Vollnhals
2005-09-13 0:10 ` Andrew Morton
2005-09-13 0:34 ` [PATCH] usb: bluetty fix old tty buffer using Jiri Slaby
2005-09-15 18:58 ` 2.6.13-mm3 (general protection fault) Dominik Karall
2005-09-15 19:34 ` Andrew Morton
2005-09-15 19:36 ` Andrew Morton
2006-01-14 17:39 ` 2.6.13-mm3 Matthias Urlichs
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=212680000.1126565451@flay \
--to=mbligh@mbligh.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nish.aravamudan@gmail.com \
--cc=paolo.ciarrocchi@gmail.com \
/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