From: Daniel Walker <dwalker@fifo99.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Andi Kleen <andi@firstfloor.org>,
LKML <linux-kernel@vger.kernel.org>,
Jeff Mahoney <jeffm@suse.com>,
Chris Mason <chris.mason@oracle.com>,
Alexander Beregalov <a.beregalov@gmail.com>,
Bron Gondwana <brong@fastmail.fm>,
Reiserfs <reiserfs-devel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrea Gelmini <andrea.gelmini@gmail.com>,
"Trenton D. Adams" <trenton.d.adams@gmail.com>,
Thomas Meyer <thomas@m3y3r.de>,
Alessio Igor Bogani <abogani@texware.it>,
Marcel Hilzinger <mhilzinger@linuxnewmedia.de>,
Edward Shishkin <edward.shishkin@gmail.com>
Subject: Re: [ANNOUNCE] Reiserfs/kill-bkl tree v2
Date: Sun, 02 Aug 2009 07:32:09 -0700 [thread overview]
Message-ID: <1249223529.6114.9.camel@desktop> (raw)
In-Reply-To: <20090802142100.GA21160@elte.hu>
On Sun, 2009-08-02 at 16:21 +0200, Ingo Molnar wrote:
> * Frederic Weisbecker <fweisbec@gmail.com> wrote:
>
> > > e.g. running all the file system stress tests from LTP would be
> > > a good idea, ideally multiple at a time on a multi processor
> > > system on a ram disk or perhaps AIM9.
> >
> > Yeah good idea. But again, I fear my laptop hasn't enough memory
> > to support big enough ramdisks mount points to host selftests.
>
> Well, dont waste too much time on it (beyond the due diligence
> level) - Andi forgot that the right way to stress-test patches is to
> get through the review process and then through the integration
> trees which have far more test exposure than any single contributor
> can test.
>
> Patch submitters cannot possibly test every crazy possibility that
> is out there - nor should they: it just doesnt scale. What we expect
> people to do is to write clean patches, to test the bits on their
> own boxes and submit them to lkml and address specific review
> feedback.
Is this the case for patches against drivers which the submitter doesn't
have or can't get a hold of?
Daniel
next prev parent reply other threads:[~2009-08-02 14:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 17:46 [ANNOUNCE] Reiserfs/kill-bkl tree v2 Frederic Weisbecker
2009-08-01 8:11 ` Andi Kleen
2009-08-01 15:53 ` Frederic Weisbecker
2009-08-02 14:21 ` Ingo Molnar
2009-08-02 14:32 ` Daniel Walker [this message]
2009-08-02 23:41 ` Frank Ch. Eigler
2009-08-03 6:09 ` Ingo Molnar
2009-08-05 22:10 ` Frederic Weisbecker
2009-08-03 5:04 ` Roland Dreier
2009-08-03 13:26 ` Chris Mason
2009-08-03 13:56 ` Ingo Molnar
2009-08-05 22:13 ` Frederic Weisbecker
2009-08-09 23:27 ` [PATCH] kill-the-bkl/reiserfs: fix early readdir offset increment Frederic Weisbecker
2009-08-05 21:59 ` [ANNOUNCE] Reiserfs/kill-bkl tree v2 Frederic Weisbecker
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=1249223529.6114.9.camel@desktop \
--to=dwalker@fifo99.com \
--cc=a.beregalov@gmail.com \
--cc=abogani@texware.it \
--cc=andi@firstfloor.org \
--cc=andrea.gelmini@gmail.com \
--cc=brong@fastmail.fm \
--cc=chris.mason@oracle.com \
--cc=edward.shishkin@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhilzinger@linuxnewmedia.de \
--cc=mingo@elte.hu \
--cc=reiserfs-devel@vger.kernel.org \
--cc=thomas@m3y3r.de \
--cc=trenton.d.adams@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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