Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261506AbVB0Wxz (ORCPT ); Sun, 27 Feb 2005 17:53:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261508AbVB0Wxy (ORCPT ); Sun, 27 Feb 2005 17:53:54 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:15834 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S261506AbVB0Wxo (ORCPT ); Sun, 27 Feb 2005 17:53:44 -0500 Date: Sun, 27 Feb 2005 22:53:39 +0000 From: Christoph Hellwig To: Andreas Gruenbacher Cc: linux-kernel@vger.kernel.org, Neil Brown , Trond Myklebust , Olaf Kirch , "Andries E. Brouwer" , Andrew Morton Subject: Re: [patch 10/16] Infrastructure and server side of nfsacl Message-ID: <20050227225339.GB2168@infradead.org> Mail-Followup-To: Christoph Hellwig , Andreas Gruenbacher , linux-kernel@vger.kernel.org, Neil Brown , Trond Myklebust , Olaf Kirch , "Andries E. Brouwer" , Andrew Morton References: <20050227152243.083308000@blunzn.suse.de> <20050227152353.191399000@blunzn.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050227152353.191399000@blunzn.suse.de> User-Agent: Mutt/1.4.1i X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 667 Lines: 14 On Sun, Feb 27, 2005 at 04:22:53PM +0100, Andreas Gruenbacher wrote: > This adds functions for encoding and decoding POSIX ACLs for the NFSACL > protocol extension, and the GETACL and SETACL RPCs. The implementation is > compatible with NFSACL in Solaris. Can you add a new fs/nfscommon/ directory instead of adding the file directly to fs/? Especially as there could be some more bits shared by nfs client and server. - 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/