public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: "J. Bruce Fields" <bfields@citi.umich.edu>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-parisc <linux-parisc@vger.kernel.org>,
	sparclinux <sparclinux@vger.kernel.org>,
	linux-s390 <linux-s390@vger.kernel.org>,
	NFS list <linux-nfs@vger.kernel.org>,
	pNFS Mailing List <pnfs@linux-nfs.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCHSET 0-5] remove unneeded nfsd #includes
Date: Tue, 24 Nov 2009 19:58:15 +0200	[thread overview]
Message-ID: <4B0C1EB7.50508@panasas.com> (raw)

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

             reply	other threads:[~2009-11-24 18:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24 17:58 Boaz Harrosh [this message]
2009-11-24 17:59 ` [PATCH 1/5] parsic: remove unused nfsd #includes Boaz Harrosh
2009-11-26 14:46   ` Boaz Harrosh
2009-11-26 21:47     ` Helge Deller
2009-11-24 18:01 ` [PATCH 2/5] sparc: " Boaz Harrosh
2009-11-25 23:19   ` David Miller
2009-11-24 18:02 ` [PATCH 3/5] s390: " Boaz Harrosh
2009-11-25  8:38   ` Martin Schwidefsky
2009-11-24 18:03 ` [PATCH 4/5] lockd: Remove unused nfsd headers #includes Boaz Harrosh
2009-11-25 20:10   ` J. Bruce Fields
2009-11-25 20:23     ` J. Bruce Fields
2009-11-26 12:39       ` Boaz Harrosh
2009-12-03 17:27         ` J. Bruce Fields
2009-11-24 18:04 ` [PATCH 5/5] vfs: nfsctl.c unused nfsd #includes Boaz Harrosh
2009-11-25 20:13   ` J. Bruce Fields
2009-11-24 18:05 ` [RFC] nfsd: Move private headers to source directory Boaz Harrosh
2009-11-25 20:14   ` J. Bruce Fields
2009-11-24 21:27 ` [PATCHSET 0-5] remove unneeded nfsd #includes Grant Grundler
2009-11-24 23:08 ` J. Bruce Fields
2009-11-25  8:42   ` Boaz Harrosh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B0C1EB7.50508@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=akpm@linux-foundation.org \
    --cc=bfields@citi.umich.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pnfs@linux-nfs.org \
    --cc=sparclinux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox