From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752788AbZHBOcI (ORCPT ); Sun, 2 Aug 2009 10:32:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752623AbZHBOcH (ORCPT ); Sun, 2 Aug 2009 10:32:07 -0400 Received: from fifo99.com ([67.223.236.141]:54869 "EHLO fifo99.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751379AbZHBOcG (ORCPT ); Sun, 2 Aug 2009 10:32:06 -0400 Subject: Re: [ANNOUNCE] Reiserfs/kill-bkl tree v2 From: Daniel Walker To: Ingo Molnar Cc: Frederic Weisbecker , Andi Kleen , LKML , Jeff Mahoney , Chris Mason , Alexander Beregalov , Bron Gondwana , Reiserfs , Al Viro , Andrea Gelmini , "Trenton D. Adams" , Thomas Meyer , Alessio Igor Bogani , Marcel Hilzinger , Edward Shishkin In-Reply-To: <20090802142100.GA21160@elte.hu> References: <20090731174642.GA6539@nowhere> <20090801081141.GA18036@basil.fritz.box> <20090801155335.GA4836@nowhere> <20090802142100.GA21160@elte.hu> Content-Type: text/plain Date: Sun, 02 Aug 2009 07:32:09 -0700 Message-Id: <1249223529.6114.9.camel@desktop> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 2009-08-02 at 16:21 +0200, Ingo Molnar wrote: > * Frederic Weisbecker 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