Re: [PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2]

2007-10-05 Thread Christoph Hellwig
On Fri, Oct 05, 2007 at 04:21:04PM +0100, David Howells wrote: > David Howells <[EMAIL PROTECTED]> wrote: > > > > Why do you move it out of line? > > > > Because otherwise every file that gets compiled that includes linux/fs.h > > will > > emit a warning that the implementation of that function

Re: [PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2]

2007-10-05 Thread David Howells
David Howells <[EMAIL PROTECTED]> wrote: > > Why do you move it out of line? > > Because otherwise every file that gets compiled that includes linux/fs.h will > emit a warning that the implementation of that function is deprecated. Or, rather, that read_inode() is deprecated. David - To

Re: [PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2]

2007-10-05 Thread David Howells
Christoph Hellwig <[EMAIL PROTECTED]> wrote: > Why do you move it out of line? Because otherwise every file that gets compiled that includes linux/fs.h will emit a warning that the implementation of that function is deprecated. David - To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2]

2007-10-05 Thread Christoph Hellwig
Why do you move it out of line? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2]

2007-10-05 Thread Christoph Hellwig
Why do you move it out of line? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2]

2007-10-05 Thread David Howells
David Howells [EMAIL PROTECTED] wrote: Why do you move it out of line? Because otherwise every file that gets compiled that includes linux/fs.h will emit a warning that the implementation of that function is deprecated. Or, rather, that read_inode() is deprecated. David - To unsubscribe

Re: [PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2]

2007-10-05 Thread David Howells
Christoph Hellwig [EMAIL PROTECTED] wrote: Why do you move it out of line? Because otherwise every file that gets compiled that includes linux/fs.h will emit a warning that the implementation of that function is deprecated. David - To unsubscribe from this list: send the line unsubscribe

Re: [PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2]

2007-10-05 Thread Christoph Hellwig
On Fri, Oct 05, 2007 at 04:21:04PM +0100, David Howells wrote: David Howells [EMAIL PROTECTED] wrote: Why do you move it out of line? Because otherwise every file that gets compiled that includes linux/fs.h will emit a warning that the implementation of that function is deprecated.

[PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2]

2007-10-04 Thread David Howells
Mark iget() and read_inode() as being obsolete and remove references to them from the documentation. Typically a filesystem will be modified such that the read_inode function becomes an internal iget function, for example the following: void thingyfs_read_inode(struct inode *inode)

[PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2]

2007-10-04 Thread David Howells
Mark iget() and read_inode() as being obsolete and remove references to them from the documentation. Typically a filesystem will be modified such that the read_inode function becomes an internal iget function, for example the following: void thingyfs_read_inode(struct inode *inode)