From: Ben Hutchings <ben@decadent.org.uk>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Neil Brown <neilb@suse.de>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] headers, nfsd: Add missing #includes to <linux/nfsd/syscall.h>
Date: Mon, 8 Aug 2011 19:06:58 +0100 [thread overview]
Message-ID: <20110808180658.GC29924@decadent.org.uk> (raw)
In-Reply-To: <20110808155538.GB904@fieldses.org>
On Mon, Aug 08, 2011 at 11:55:38AM -0400, J. Bruce Fields wrote:
> On Mon, Aug 08, 2011 at 02:29:29PM +0100, Ben Hutchings wrote:
> > <linux/nfsd/syscall.h> uses the NFS_MAXPATHLEN and NFS_FHSIZE macros
> > defined in <linux/nfs.h>, and struct knfsd_fh defined in
> > <linux/nfsd/nfsfh.h>.
>
> Well, the real bug is that this file exists at all.
OK. I've been more-or-less mechanically fixing headers and I don't
have any particular expectations of this one.
> Neil sent this
> http://marc.info/?l=linux-nfs&m=130881392416899&w=2 in a while ago but I
> didn't want to attempt to merge something that touched every arch
> directory. I wonder what we should do....
[...]
So long as it's cc'd to linux-arch and linux-kernel, I don't think
that's going to be a problem. Yes it might conflict, but Linus
(and sfr) can cope with such conflicts.
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
next prev parent reply other threads:[~2011-08-08 18:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 13:29 [PATCH] headers, nfsd: Add missing #includes to <linux/nfsd/syscall.h> Ben Hutchings
2011-08-08 15:55 ` J. Bruce Fields
2011-08-08 18:06 ` Ben Hutchings [this message]
2011-08-26 22:03 ` [PATCH] All Arch: remove linkage for sys_nfsservctl system call J. Bruce Fields
2011-08-26 23:32 ` Ben Hutchings
2011-08-26 23:52 ` J. Bruce Fields
2011-08-27 0:01 ` David Miller
2011-08-27 14:39 ` Mike Frysinger
2011-08-28 21:12 ` David Miller
2011-08-28 23:50 ` Tony Breeds
2011-08-29 22:57 ` Stephen Rothwell
2011-08-29 23:11 ` NeilBrown
2011-08-31 13:46 ` J. Bruce Fields
2011-08-31 10:15 ` David Howells
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=20110808180658.GC29924@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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