From: Ingo Molnar <mingo@elte.hu>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Charles Edward Lever <Chuck.Lever@oracle.com>,
Zimny Lech <napohybelskurwysynom2010@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-nfs@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: linux-next: Tree for October 6
Date: Tue, 26 Oct 2010 14:41:13 +0200 [thread overview]
Message-ID: <20101026124113.GA10872@elte.hu> (raw)
In-Reply-To: <1288096333.3123.9.camel@heimdal.trondhjem.org>
* Trond Myklebust <Trond.Myklebust@netapp.com> wrote:
> Anyhow, does the following fix the bug?
Thanks, trying it.
> Stephen Rothwell reports:
>
> > /home/test/linux-2.6/fs/nfs/nfsroot.c: In function 'nfs_root_debug':
> > /home/test/linux-2.6/fs/nfs/nfsroot.c:110:2: error: 'nfs_debug'
> > undeclared (first use in this function)
> > /home/test/linux-2.6/fs/nfs/nfsroot.c:110:2: note: each undeclared
> > identifier is reported only once for each function it appears in
> > make[3]: *** [fs/nfs/nfsroot.o] Error 1
> > make[2]: *** [fs/nfs] Error 2
> > make[1]: *** [fs] Error 2
> > make: *** [sub-make] Error 2
>
> Which is caused by commit 306a075362a288683f6346185f97dd0e06df19da
> (NFS: Allow NFSROOT debugging messages to be enabled dynamically)
>
> Fix is to disable this code when RPC_DEBUG is disabled.
>
> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
The commit also needs this tag:
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Thanks,
Ingo
next prev parent reply other threads:[~2010-10-26 12:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 5:36 linux-next: Tree for October 6 Stephen Rothwell
2010-10-06 6:25 ` Zimny Lech
2010-10-06 6:48 ` Stephen Rothwell
2010-10-06 18:07 ` Zimny Lech
2010-10-06 18:12 ` Christoph Lameter
2010-10-06 18:15 ` Pekka Enberg
2010-10-06 18:20 ` Christoph Lameter
2010-10-06 19:23 ` Pekka Enberg
2010-10-06 20:09 ` Christoph Lameter
2010-10-06 18:16 ` Zimny Lech
2010-10-06 18:14 ` Zimny Lech
2010-10-06 18:22 ` Zimny Lech
2010-10-26 8:08 ` Ingo Molnar
[not found] ` <20101026080822.GA10520-X9Un+BFzKDI@public.gmane.org>
2010-10-26 12:32 ` Trond Myklebust
2010-10-26 12:41 ` Ingo Molnar [this message]
2010-10-26 12:57 ` Stephen Rothwell
[not found] ` <20101026124113.GA10872-X9Un+BFzKDI@public.gmane.org>
2010-10-26 17:52 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2009-10-06 5:52 Stephen Rothwell
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=20101026124113.GA10872@elte.hu \
--to=mingo@elte.hu \
--cc=Chuck.Lever@oracle.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=napohybelskurwysynom2010@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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).