From: Jason Baron <jbaron@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for October 20
Date: Mon, 20 Oct 2008 13:35:45 -0400 [thread overview]
Message-ID: <20081020173545.GB3161@redhat.com> (raw)
In-Reply-To: <20081020235904.2f9a8db4.sfr@canb.auug.org.au>
On Mon, Oct 20, 2008 at 11:59:04PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's tree will not build for powerpc allyesconfig (libc aborts the
> link due to a free() problem), sparc(32) defconfig and probably some
> other configurations.
>
hmmm...yeah, on x86_64 i've hit:
CC [M] net/9p/protocol.o
LD [M] net/9p/9pnet.o
LD [M] net/9p/9pnet_virtio.o
Building modules, stage 2.
MODPOST 1616 modules
ERROR: "p9_debug_level" [net/9p/9pnet.ko] undefined!
seems to be resolved by this simple patch:
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);
next prev parent reply other threads:[~2008-10-20 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 12:59 linux-next: Tree for October 20 Stephen Rothwell
2008-10-20 17:35 ` Jason Baron [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-20 5:20 Stephen Rothwell
2010-10-21 13:09 ` Christoph Hellwig
2010-10-21 13:21 ` Zimny Lech
2010-10-25 8:47 ` Michal Marek
2010-10-26 16:22 ` Arnaud Lacombe
2010-10-27 21:20 ` Michal Marek
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=20081020173545.GB3161@redhat.com \
--to=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).