From: Zan Lynx <zlynx@acm.org>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to make -mm a more viable testbed (was: [PATCH] [1/12] x86: Work around mmio config space quirk on AMD)
Date: Mon, 13 Aug 2007 14:40:06 -0600 [thread overview]
Message-ID: <1187037607.7855.21.camel@localhost> (raw)
In-Reply-To: <200708130808.46989.a1426z@gawab.com>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
On Mon, 2007-08-13 at 08:08 +0300, Al Boldi wrote:
> Linus Torvalds wrote:
> > On Sun, 12 Aug 2007, Dave Jones wrote:
> > >
> > > This does make me wonder, why these weren't caught in -mm ?
> >
> > I'm worried that -mm isn't getting a lot of exposure these days. People do
> > run it, but I wonder how many..
>
> Well, I'm not running it because it's got too much garbage in it, which makes
> it a pretty unrealistic testbed. And to make matters worse, I also stay
> away from rc's as a consequence.
>
> To make -mm more viable, it may be advisable to restructure -mm in such a way
> as to be a Kconfig option to mainline. This would probably involve some
> patch management functionality to apply experimental submissions on a
> per-patch basis, as opposed to being a 'take it or leave it slam onto
> mainline' patch.
I thought most people running -mm were running klive, which shou
ld tell kernel versions, uptime and other things. I run it, anyway.
http://klive.cpushare.com/
--
Zan Lynx <zlynx@acm.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-08-13 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 5:08 How to make -mm a more viable testbed (was: [PATCH] [1/12] x86: Work around mmio config space quirk on AMD) Al Boldi
2007-08-13 20:40 ` Zan Lynx [this message]
2007-08-13 21:03 ` Valdis.Kletnieks
2007-08-13 21:09 ` Dave Jones
2007-08-13 23:07 ` Zan Lynx
2007-08-13 23:09 ` Dave Jones
2007-08-14 9:45 ` How to make -mm a more viable testbed Tilman Schmidt
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=1187037607.7855.21.camel@localhost \
--to=zlynx@acm.org \
--cc=a1426z@gawab.com \
--cc=linux-kernel@vger.kernel.org \
/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).