Date: Tue, 5 Dec 2006 14:49:13 -0800
From: Andrew Morton <akpm@osdl.org>
To: Josef Sipek <jsipek@fsl.cs.sunysb.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] fsstack: Fix up ecryptfs's fsstack usage
Message-Id: <20061205144913.fea98946.akpm@osdl.org>
In-Reply-To: <20061205223807.GA7300@filer.fsl.cs.sunysb.edu>
References: <20061204204024.2401148d.akpm@osdl.org>
	<20061205191824.GB2240@filer.fsl.cs.sunysb.edu>
	<20061205192231.GD2240@filer.fsl.cs.sunysb.edu>
	<20061205142831.9cb3e91c.akpm@osdl.org>
	<20061205223807.GA7300@filer.fsl.cs.sunysb.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 968
Lines: 22

On Tue, 5 Dec 2006 17:38:07 -0500
Josef Sipek <jsipek@fsl.cs.sunysb.edu> wrote:

> > When your patches are queued in -mm please do test them there, and review
> > others' changes to them, and raise patches against them.  Raising patches
> > against one's private tree and not testing the code which is planned to be
> > merged can introduce errors.
> 
> Sorry about that. I noticed your fix, and the one by Adrian. And I did add
> them to my fsstack queue.

you don't have an fsstack queue any more ;)

Please, I really do want developers to test their code in -mm once I've
merged it.  What happens if there's some nasty interaction between your
patch and someone else's?  We'll not find out about it and it'll get
merged.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/