public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@redhat.com>
To: "Alejandro Riveira Fernández" <alejandro.riveira@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	ericvh@gmail.com, v9fs-developer@lists.sourceforge.net,
	lucho@ionkov.net
Subject: Re: [net/9p/9pnet.c] Compile error
Date: Mon, 20 Oct 2008 16:49:54 -0400	[thread overview]
Message-ID: <20081020204954.GC3161@redhat.com> (raw)
In-Reply-To: <1224530845.22829.4.camel@varda>

On Mon, Oct 20, 2008 at 09:27:25PM +0200, Alejandro Riveira Fernández wrote:
> Current Git
>  v2.6.27-6030-g6da0b38
> 
>  I get a build error
> 
> Kernel: arch/x86/boot/bzImage is ready  (#17)
>   Building modules, stage 2.
>   MODPOST 571 modules
> ERROR: "p9_debug_level" [net/9p/9pnet.ko] undefined!
> make[3]: *** [__modpost] Error 1
> make[2]: *** [modules] Error 2
> make[1]: *** [sub-make] Error 2
> make: *** [all] Error 2
> 

hi,

Yes, i hit that too...the patch below resolved it for me.

thanks,

-Jason


Signed-off-by: Jason Baron <jbaron@redhat.com>

diff --git a/net/9p/protocol.c b/net/9p/protocol.c
index 29be524..ebf819e 100644
--- a/net/9p/protocol.c
+++ b/net/9p/protocol.c
@@ -542,8 +542,10 @@ int p9pdu_finalize(struct p9_fcall *pdu)
 	err = p9pdu_writef(pdu, 0, "d", size);
 	pdu->size = size;
 
+#ifdef CONFIG_NET_9P_DEBUG
 	if ((p9_debug_level & P9_DEBUG_PKT) == P9_DEBUG_PKT)
 		p9pdu_dump(0, pdu);
+#endif
 
 	P9_DPRINTK(P9_DEBUG_9P, ">>> size=%d type: %d tag: %d\n", pdu->size,
 							pdu->id, pdu->tag);

  reply	other threads:[~2008-10-20 20:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 19:27 [net/9p/9pnet.c] Compile error Alejandro Riveira Fernández
2008-10-20 20:49 ` Jason Baron [this message]
2008-10-20 21:04   ` Eric Van Hensbergen
2008-10-21  9:17     ` Alejandro Riveira Fernández

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=20081020204954.GC3161@redhat.com \
    --to=jbaron@redhat.com \
    --cc=alejandro.riveira@gmail.com \
    --cc=ericvh@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucho@ionkov.net \
    --cc=v9fs-developer@lists.sourceforge.net \
    /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