From: Marcel Holtmann <marcel@holtmann.org>
To: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Cc: "David S. Miller" <davem@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Problem with CONFIG_SYSCTL disabled
Date: Mon, 19 Jan 2004 15:09:29 +0100 [thread overview]
Message-ID: <1074521369.6070.99.camel@pegasus> (raw)
In-Reply-To: <20040119.224603.71004956.yoshfuji@linux-ipv6.org>
Hi,
> > In file included from drivers/net/net_init.c:53:
> > include/net/neighbour.h:216: error: parse error before "proc_handler"
> > include/net/neighbour.h:216: warning: function declaration isn't a prototype
>
> ===== include/net/neighbour.h 1.5 vs edited =====
> --- 1.5/include/net/neighbour.h Thu Jan 15 17:58:09 2004
> +++ edited/include/net/neighbour.h Mon Jan 19 22:42:24 2004
> @@ -47,9 +47,7 @@
> #include <linux/skbuff.h>
>
> #include <linux/err.h>
> -#ifdef CONFIG_SYSCTL
> #include <linux/sysctl.h>
> -#endif
>
> #define NUD_IN_TIMER (NUD_INCOMPLETE|NUD_DELAY|NUD_PROBE)
> #define NUD_VALID (NUD_PERMANENT|NUD_NOARP|NUD_REACHABLE|NUD_PROBE|NUD_STALE|NUD_DELAY)
so it is not needed to wrap the inclusion of linux/sysctl.h around
#ifdef's, but why is it done so many times?
net/core/neighbour.c
net/ipv4/devinet.c
net/ipv4/arp.c
net/ipv4/route.c
net/ipv4/netfilter/ip_conntrack_standalone.c
net/ipv6/route.c
net/ipv6/addrconf.c
net/ipv6/ndisc.c
net/ipv6/icmp.c
net/appletalk/sysctl_net_atalk.c
net/bridge/br_netfilter.c
Regards
Marcel
next prev parent reply other threads:[~2004-01-19 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 13:30 Problem with CONFIG_SYSCTL disabled Marcel Holtmann
2004-01-19 13:46 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-19 14:09 ` Marcel Holtmann [this message]
2004-01-19 14:21 ` YOSHIFUJI Hideaki / 吉藤英明
[not found] ` <1074524771.21244.7.camel@telecentrolivre>
2004-01-19 17:40 ` David S. 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=1074521369.6070.99.camel@pegasus \
--to=marcel@holtmann.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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