From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>
Subject: Re: linux-next: Tree for June 11 (cnic)
Date: Thu, 11 Jun 2009 15:21:12 -0700 [thread overview]
Message-ID: <4A318358.20804@oracle.com> (raw)
In-Reply-To: <20090611191420.1f4d5e4f.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20090610:
In 2 separate builds:
ERROR: "ip_route_output_key" [drivers/net/cnic.ko] undefined!
when CONFIG_INET=n
and
drivers/net/cnic.c:2520: error: implicit declaration of function '__symbol_get'
when CONFIG_MODULES=n
--
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/
next parent reply other threads:[~2009-06-11 22:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090611191420.1f4d5e4f.sfr@canb.auug.org.au>
2009-06-11 22:21 ` Randy Dunlap [this message]
2009-06-18 10:16 ` linux-next: Tree for June 11 (cnic) Kamalesh Babulal
[not found] ` <4A31869B.3050901@oracle.com>
2009-06-12 22:59 ` [PATCH -next] ieee802154: fix kconfig bool/tristate muckup Randy Dunlap
2009-06-13 10:57 ` Sergey Lapin
2009-06-14 6:37 ` David Miller
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=4A318358.20804@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@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).