From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 4/5] xattr handlers: Pass handler to operations instead of flags Date: Wed, 16 Sep 2015 07:16:14 -0700 Message-ID: <20150916141614.GB16005@infradead.org> References: <1441367842-25079-1-git-send-email-agruenba@redhat.com> <1441367842-25079-5-git-send-email-agruenba@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Alexander Viro , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Artem Bityutskiy , Adrian Hunter , linux-mtd@lists.infradead.org, Richard Weinberger , Eric Van Hensbergen , Ron Minnich , Latchesar Ionkov , v9fs-developer@lists.sourceforge.net To: Andreas Gruenbacher Return-path: Content-Disposition: inline In-Reply-To: <1441367842-25079-5-git-send-email-agruenba@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri, Sep 04, 2015 at 01:57:21PM +0200, Andreas Gruenbacher wrote: > The xattr_handler operations are currently all passed a file system specific > flags value which the operations can use to disambiguate between different > handlers; some file systems use that to distinguish the xattr namespace, for > example. In some oprations, it would be useful to also have access to the > handler prefix. To allow that, pass a pointer to the handler to operations > instead of the flags value alone. Looks ok, but the more usual calling convention would be to pass the handler as the first argument.