From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: NFS related randconfig failure on powerpc ('nfs_debug' undeclared)
Date: Thu, 15 Mar 2012 11:52:57 -0400 [thread overview]
Message-ID: <4F621059.7040106@windriver.com> (raw)
In-Reply-To: <1331778292.9623.22.camel@lade.trondhjem.org>
On 12-03-14 10:24 PM, Myklebust, Trond wrote:
> On Wed, 2012-03-14 at 19:25 -0400, Paul Gortmaker wrote:
>> Just a heads up that linux-next builds found this;
>>
>> fs/nfs/nfs4xdr.c:3443:27: error: 'nfs_debug' undeclared (first use in
>> this function)
>> make[3]: *** [fs/nfs/nfs4xdr.o] Error 1
>> make[2]: *** [fs/nfs] Error 2
>> make[1]: *** [fs] Error 2
>> make: *** [sub-make] Error 2
>>
>> Full build log at:
>>
>> http://kisskb.ellerman.id.au/kisskb/buildresult/5871973/
>>
>> Paul.
>
> Hi Paul,
>
> Does the following fix work for you?
Yes. (compile tested, that is).
Thanks,
Paul.
>
> Thanks!
> Trond
> 8<------------------------------------------------------
> From 95a13f7b33be87d85d8e6652126a3f4d64d164db Mon Sep 17 00:00:00 2001
> From: Trond Myklebust <Trond.Myklebust@netapp.com>
> Date: Wed, 14 Mar 2012 21:55:01 -0400
> Subject: [PATCH] NFS: Fix a compile error when !defined NFS_DEBUG
>
> We should use the 'ifdebug' wrapper rather than trying to inline
> tests of nfs_debug, so that the code compiles correctly when we
> don't define NFS_DEBUG.
>
> Reported-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
> ---
> fs/nfs/nfs4xdr.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/nfs/nfs4xdr.c b/fs/nfs/nfs4xdr.c
> index f7e064d..c74fdb1 100644
> --- a/fs/nfs/nfs4xdr.c
> +++ b/fs/nfs/nfs4xdr.c
> @@ -3440,7 +3440,7 @@ static int decode_pathname(struct xdr_stream *xdr, struct nfs4_pathname *path)
> status = decode_opaque_inline(xdr, &component->len, &component->data);
> if (unlikely(status != 0))
> goto out_eio;
> - if (unlikely(nfs_debug & NFSDBG_XDR))
> + ifdebug (XDR)
> pr_cont("%s%.*s ",
> (path->ncomponents != n ? "/ " : ""),
> component->len, component->data);
prev parent reply other threads:[~2012-03-15 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 23:25 NFS related randconfig failure on powerpc ('nfs_debug' undeclared) Paul Gortmaker
2012-03-15 2:24 ` Myklebust, Trond
2012-03-15 15:52 ` Paul Gortmaker [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=4F621059.7040106@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=Trond.Myklebust@netapp.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.