From: Bryan Schumaker <bjschuma@netapp.com>
To: Danny Kukawka <danny.kukawka@bisect.de>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
Danny Kukawka <dkukawka@suse.de>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs/nfs/dns_resolve.c: included linux/nfs_fs.h twice
Date: Thu, 16 Feb 2012 09:18:04 -0500 [thread overview]
Message-ID: <4F3D101C.6080805@netapp.com> (raw)
In-Reply-To: <1329400481-31627-1-git-send-email-danny.kukawka@bisect.de>
On 02/16/12 08:54, Danny Kukawka wrote:
> fs/nfs/dns_resolve.c: included 'linux/nfs_fs.h' twice. No need
^^^^^^^^^^^^^
You probably meant idamp.c here...
Good catch. My idmapper fallback changes from a few weeks ago should have already done this see:
e6499c6f4b5f56a16f8b8ef60529c1da28b13aea NFS: Fall back on old idmapper if request_key() fails
3cd0f37a2cc9e4d6188df10041a2441eaa41d991 NFS: Keep idmapper include files in one place
in Trond's nfs-for-next branch.
- Bryan
> to include it in the 'CONFIG_NFS_USE_NEW_IDMAPPER not defined'
> block since it's already included at the top of the file.
>
> Signed-off-by: Danny Kukawka <danny.kukawka@bisect.de>
> ---
> fs/nfs/idmap.c | 2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
>
> diff --git a/fs/nfs/idmap.c b/fs/nfs/idmap.c
> index 2c05f19..1526b5f 100644
> --- a/fs/nfs/idmap.c
> +++ b/fs/nfs/idmap.c
> @@ -374,8 +374,6 @@ int nfs_map_gid_to_group(const struct nfs_server *server, __u32 gid, char *buf,
> #include <linux/workqueue.h>
> #include <linux/sunrpc/rpc_pipe_fs.h>
>
> -#include <linux/nfs_fs.h>
> -
> #include "nfs4_fs.h"
>
> #define IDMAP_HASH_SZ 128
next prev parent reply other threads:[~2012-02-16 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 13:54 [PATCH] fs/nfs/dns_resolve.c: included linux/nfs_fs.h twice Danny Kukawka
2012-02-16 14:18 ` Bryan Schumaker [this message]
2012-02-16 14:23 ` Bryan Schumaker
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=4F3D101C.6080805@netapp.com \
--to=bjschuma@netapp.com \
--cc=Trond.Myklebust@netapp.com \
--cc=danny.kukawka@bisect.de \
--cc=dkukawka@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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