Home
last modified time | relevance | path

Searched hist:"27 c72b04" (Results 1 – 12 of 12) sorted by relevance

/openbmc/linux/fs/jffs2/
H A Dbuild.c27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
H A Dxattr.c27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
H A Dwrite.c27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
H A Dnodelist.h27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
H A Dnodemgmt.c27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
H A Dgc.c27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
H A Derase.c27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
H A Dreadinode.c27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
H A Dscan.c27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
H A Ddir.c27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
H A Dwbuf.c27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
H A Dfs.c27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
27c72b04 Thu May 01 12:47:17 CDT 2008 David Woodhouse <dwmw2@infradead.org> [JFFS2] Track parent inode for directories (for NFS export)

To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>