[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20070807182044.06ce4675.jlayton@redhat.com>
Date: Tue, 7 Aug 2007 18:20:44 -0400
From: Jeff Layton <jlayton@...hat.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
v9fs-developer@...ts.sourceforge.net, zippel@...ux-m68k.org,
dhowells@...hat.com, linux-cifs-client@...ts.samba.org,
codalist@...EMANN.coda.cs.cmu.edu, joel.becker@...cle.com,
linux-ext4@...r.kernel.org, fuse-devel@...ts.sourceforge.net,
cluster-devel@...hat.com,
user-mode-linux-user@...ts.sourceforge.net,
mikulas@...ax.karlin.mff.cuni.cz, wli@...omorphy.com,
jffs-dev@...s.com, jfs-discussion@...ts.sourceforge.net,
ocfs2-devel@....oracle.com, reiserfs-devel@...r.kernel.org,
bfennema@...con.csc.calpoly.edu, xfs@....sgi.com
Subject: Re: [PATCH 01/25] VFS: move attr_kill logic from notify_change into
helper function
On Tue, 7 Aug 2007 21:51:49 +0100
Christoph Hellwig <hch@...radead.org> wrote:
> > +void attr_kill_to_mode(struct inode *inode, struct iattr *attr)
>
> This function badly needs a kerneldoc description. Also I can't say
> I like the name a lot, but without a clearly better idea I should
> probably not complain :)
>
Thanks for the comments.
I'm not thrilled with the name either, but kill_suid and *remove_suid
were already taken, and I really didn't want to name this something too
similar since there are already so many similarly named functions that
don't do the same thing. I'm definitely open to suggestions for
something different.
> We should at least add a generic_ prefix to indicate it's a generic
> helper valid for most filesystem (and the kerneldoc comment can explain
> the details)
>
Both good suggestions. I'll plan to incorporate them in the next
respin of the set.
Thanks,
--
Jeff Layton <jlayton@...hat.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists