On Fri, 22 Jun 2001, Anton Altaparmakov wrote:
> >-#define NFS_FH(inode) (&(inode)->u.nfs_i.fh)
[snip]
> >+#define NFS_FH(inode) (&NFS_I(inode)->fh)
>
> Al,
>
> Just as a matter of interest: why do you define NFS_I as a static inline
> function while you leave NFS_FS as a preprocessor macro? I assume there is
> some good reason I am missing to do this... (could it be side effects?)
Basically, laziness. It would be a bit cleaner as inline, but unlike
NFS_I() it was already there, so it was left as it was, aside of the
effect of global replacement (inode->u.nfs_i.foo to NFS_I(inode)->foo).
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]