From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 1/2] sanitize xattr handler prototypes Date: Thu, 12 Nov 2009 18:56:44 +0100 Message-ID: <20091112175644.GA10147@lst.de> References: <20091103154448.GB23101@lst.de> <1257268307.6052.764.camel@localhost.localdomain> <20091110121941.c814d4c9.akpm@linux-foundation.org> <1257933520.2718.6.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andrew Morton , Christoph Hellwig , viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org To: Steven Whitehouse Return-path: Received: from verein.lst.de ([213.95.11.210]:50917 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753471AbZKLR5E (ORCPT ); Thu, 12 Nov 2009 12:57:04 -0500 Content-Disposition: inline In-Reply-To: <1257933520.2718.6.camel@localhost.localdomain> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, Nov 11, 2009 at 09:58:40AM +0000, Steven Whitehouse wrote: > The changes required to allow the patch to apply are pretty small, but > I'm not really sure about the best path forward at this > point :( Updating the patch is easy, but the question is which tree > should it go in when its been updated? Given that you have a subsystem tree and these patches are in -mm only for now I think you should keep your tree as-is and this patch should be rebased. Given that you figure out how easy that is can you do it for me? That'd avoid having to pull yet another tree onto my far too small SSD :)