[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B0C1EB7.50508@panasas.com>
Date: Tue, 24 Nov 2009 19:58:15 +0200
From: Boaz Harrosh <bharrosh@...asas.com>
To: "J. Bruce Fields" <bfields@...i.umich.edu>,
Linux Kernel <linux-kernel@...r.kernel.org>,
linux-parisc <linux-parisc@...r.kernel.org>,
sparclinux <sparclinux@...r.kernel.org>,
linux-s390 <linux-s390@...r.kernel.org>,
NFS list <linux-nfs@...r.kernel.org>,
pNFS Mailing List <pnfs@...ux-nfs.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: [PATCHSET 0-5] remove unneeded nfsd #includes
Some arch files had unneeded #includes directives from linux/nfsd/*.
Some vfs files had unneeded #includes directives from linux/nfsd/*.
In an effort to move some of the now public nfsd headers to the source
directory, submitted a cleanup.
I have cross compiled sparc64 and s390, parsic needs testing. Please ARCH
people sends ACKs, or take these patches through your trees.
patches:
[PATCH 1/5] parsic: remove unused nfsd #includes
Some kind soul, please compile with this patch? compile
is all that's needed.
[PATCH 2/5] sparc: remove unused nfsd #includes
[PATCH 3/5] s390: remove unused nfsd #includes
These two were cross compiled. Should we submit them through
nfsd tree or the ARCH trees?
[PATCH 4/5] vfs: nfsctl.c unused nfsd #includes
[PATCH 5/5] lockd: Remove unused nfsd headers #includes
Can these patches go through the nfsd tree?
Who's ACKs should we collect? Andrew?
Bruce Hi
With this set applied, the only nfsd files used publicly are:
const.h export.h nfsfh.h stats.h syscall.h
These files can be moved to source folder:
cache.h debug.h nfsd.h state.h xdr3.h xdr4.h xdr.h
Why is debug.h exported from Kernel? (include/linux/nfsd/Kbuild)
So just to see how this move might look like see last patch:
[RFC] nfsd: Move private headers to source directory
This patch was compiled, as well, on x86(32/64), sparc64, s390
Thanks
Boaz
--
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