From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: get rid of include/linux/nfsd
Date: Tue, 6 May 2014 15:09:26 -0400 [thread overview]
Message-ID: <20140506190926.GI18281@fieldses.org> (raw)
In-Reply-To: <1399397836-31948-1-git-send-email-hch@lst.de>
On Tue, May 06, 2014 at 07:37:12PM +0200, Christoph Hellwig wrote:
> Now that all user-visible headers are in include/uapi there is nothing
> left there which shouldn't rather be under fs/nfsd/.
Makes sense, thanks, applying.
I'll try to get a for-3.16 branch pushed out today or tomorrow.
--b.
prev parent reply other threads:[~2014-05-06 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 17:37 get rid of include/linux/nfsd Christoph Hellwig
2014-05-06 17:37 ` [PATCH 1/4] nfsd: remove <linux/nfsd/nfsfh.h> Christoph Hellwig
2014-05-06 17:37 ` [PATCH 2/4] nfsd: move <linux/nfsd/export.h> to fs/nfsd Christoph Hellwig
2014-05-06 17:37 ` [PATCH 3/4] nfsd: move <linux/nfsd/stats.h> " Christoph Hellwig
2014-05-06 17:37 ` [PATCH 4/4] nfsd: remove <linux/nfsd/debug.h> Christoph Hellwig
2014-05-06 19:09 ` J. Bruce Fields [this message]
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=20140506190926.GI18281@fieldses.org \
--to=bfields@fieldses.org \
--cc=hch@lst.de \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).