From: Wang Chen <wangchen@cn.fujitsu.com>
To: David Miller <davem@davemloft.net>
Cc: Ingo Molnar <mingo@elte.hu>,
viro@ZenIV.linux.org.uk, NETDEV <netdev@vger.kernel.org>
Subject: [PATCH] net/ipv4/route.c: fix build error
Date: Fri, 01 Aug 2008 09:40:59 +0800 [thread overview]
Message-ID: <489269AB.8050706@cn.fujitsu.com> (raw)
In-Reply-To: <20080727214250.GA5917@elte.hu>
Dave, the build error keeps showing several days.
From: Ingo Molnar <mingo@elte.hu>
Date: Sun, 27 Jul 2008 23:51:45 +0200
Subject: [PATCH] net/ipv4/route.c: fix build error
fix:
net/ipv4/route.c: In function 'ip_static_sysctl_init':
net/ipv4/route.c:3225: error: 'ipv4_route_path' undeclared (first use in this function)
net/ipv4/route.c:3225: error: (Each undeclared identifier is reported only once
net/ipv4/route.c:3225: error: for each function it appears in.)
net/ipv4/route.c:3225: error: 'ipv4_route_table' undeclared (first use in this function)
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
net/ipv4/route.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/net/ipv4/route.c b/net/ipv4/route.c
index 380d647..d7bf056 100644
--- a/net/ipv4/route.c
+++ b/net/ipv4/route.c
@@ -3222,7 +3222,9 @@ int __init ip_rt_init(void)
*/
void __init ip_static_sysctl_init(void)
{
+#ifdef CONFIG_SYSCTL
register_sysctl_paths(ipv4_route_path, ipv4_route_table);
+#endif
}
EXPORT_SYMBOL(__ip_select_ident);
--
next parent reply other threads:[~2008-08-01 1:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080727075933.GB28946@ZenIV.linux.org.uk>
[not found] ` <20080727.044118.102038262.davem@davemloft.net>
[not found] ` <20080727213905.GA4499@elte.hu>
[not found] ` <20080727214250.GA5917@elte.hu>
2008-08-01 1:40 ` Wang Chen [this message]
2008-08-01 3:51 ` [PATCH] net/ipv4/route.c: fix build error David Miller
2008-08-06 13:04 ` Paulius Zaleckas
2008-08-07 1:31 ` 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=489269AB.8050706@cn.fujitsu.com \
--to=wangchen@cn.fujitsu.com \
--cc=davem@davemloft.net \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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).