public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: "J. Bruce Fields" <bfields@citi.umich.edu>,
	NFS list <linux-nfs@vger.kernel.org>,
	pNFS Mailing List <pnfs@linux-nfs.org>
Subject: [PATCHSET 00/12 repost] nfsd: #includes cleanup
Date: Thu, 03 Dec 2009 20:26:24 +0200	[thread overview]
Message-ID: <4B1802D0.8060206@panasas.com> (raw)


Hi Bruce

I'm reposting the all set together

There are two patches that people have said will go through
other trees (see below). So either wait with patch 12/12 after
they get into Linus. Or also submit them through nfsd, it should
not cause any problems to post the same patch from two sub-trees,
right?

(For the things done here please let it sit in linux-next for
 a couple of nights)

[PATCH 01/12] nfsd: Remove nfsfh.h dependency on sunrpc
[PATCH 02/12] sunrpc: Clean never used include files   
[PATCH 03/12] nfsd: Fix independence of a few nfsd related headers
[PATCH 04/12] nfsd: Headers Independence and include cleanups     
[PATCH 05/12] nfsd: Source files #include cleanups

	First batch

[PATCH 06/12] compat.c: Remove dependence on nfsd private headers
[PATCH 07/12] parsic: remove un-used nfsd #includes

	This patch we have ACK on

[PATCH 08/12] sparc: remove un-used nfsd #includes
[PATCH 09/12] s390: remove un-used nfsd #includes

	These two were reported as submitted into ARCH tree for 2.6.33

[PATCH 10/12] lockd: Remove un-used nfsd headers #includes
[PATCH 11/12] vfs: nfsctl.c un-used nfsd #includes

[PATCH 12/12] nfsd: Move private headers to source directory
	
	this patch is the only one that depends on all
	the other parts, and need all patches in.
	(And will cause Benny's tree to adjust)

Thanks
Boaz


             reply	other threads:[~2009-12-03 18:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 18:26 Boaz Harrosh [this message]
2009-12-03 18:28 ` [PATCH 01/12] nfsd: Remove nfsfh.h dependency on sunrpc Boaz Harrosh
2009-12-05  1:01   ` J. Bruce Fields
2009-12-03 18:28 ` [PATCH 02/12] sunrpc: Clean never used include files Boaz Harrosh
2009-12-03 18:28 ` [PATCH 03/12] nfsd: Fix independence of a few nfsd related headers Boaz Harrosh
2009-12-03 18:28 ` [PATCH 04/12] nfsd: Headers Independence and include cleanups Boaz Harrosh
2009-12-03 18:29 ` [PATCH 05/12] nfsd: Source files #include cleanups Boaz Harrosh
2009-12-03 18:29 ` [PATCH 06/12] compat.c: Remove dependence on nfsd private headers Boaz Harrosh
2009-12-03 18:29 ` [PATCH 07/12] parsic: remove un-used nfsd #includes Boaz Harrosh
2009-12-03 18:29 ` [PATCH 08/12] sparc: " Boaz Harrosh
2009-12-03 18:30 ` [PATCH 09/12] s390: " Boaz Harrosh
2009-12-03 18:30 ` [PATCH 10/12] lockd: Remove un-used nfsd headers #includes Boaz Harrosh
2009-12-03 18:30 ` [PATCH 11/12] vfs: nfsctl.c un-used nfsd #includes Boaz Harrosh
2009-12-03 18:30 ` [PATCH 12/12] nfsd: Move private headers to source directory Boaz Harrosh
2009-12-03 18:37 ` [pnfs] [PATCHSET 00/12 repost] nfsd: #includes cleanup Boaz Harrosh
2009-12-03 19:01   ` J. Bruce Fields
2009-12-05  1:00 ` J. Bruce Fields
2009-12-05  1:03   ` J. Bruce Fields
2009-12-05  1:04     ` J. Bruce Fields
2009-12-06  9:36       ` 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=4B1802D0.8060206@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=bfields@citi.umich.edu \
    --cc=linux-nfs@vger.kernel.org \
    --cc=pnfs@linux-nfs.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