From: Cong Wang <xiyou.wangcong@gmail.com>
To: Gao feng <gaofeng@cn.fujitsu.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH 2/3] net: dev: fix build failed when procfs is disabled
Date: Tue, 19 Feb 2013 20:02:51 +0800 [thread overview]
Message-ID: <512369EB.7090209@gmail.com> (raw)
In-Reply-To: <1361270592-19492-2-git-send-email-gaofeng@cn.fujitsu.com>
On 02/19/2013 06:43 PM, Gao feng wrote:
> commit 900ff8c6321418dafa03c22e215cb9646a2541b9
> "net: move procfs code to net/core/net-procfs.c"
> missed define dev_mcast_init when CONFIG_PROC
> isn't configured.
>
> Cc: Cong Wang <xiyou.wangcong@gmail.com>
> Signed-off-by: Gao feng <gaofeng@cn.fujitsu.com>
> ---
> include/linux/netdevice.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> index f111b4f..91f6c7b 100644
> --- a/include/linux/netdevice.h
> +++ b/include/linux/netdevice.h
> @@ -2693,8 +2693,10 @@ extern void net_disable_timestamp(void);
>
> #ifdef CONFIG_PROC_FS
> extern int __init dev_proc_init(void);
> +extern void __init dev_mcast_init(void);
> #else
> #define dev_proc_init() 0
> +#define dev_mcast_init() {}
> #endif
>
> extern int netdev_class_create_file(struct class_attribute *class_attr);
>
Thanks for catching this!
I forgot to test !CONFIG_PROC_FS case again after grabbing the mcast piece.
I have a better fix, which moves dev_mcast_init() to dev_proc_init(),
will post it right now.
next prev parent reply other threads:[~2013-02-19 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 10:43 [PATCH 1/3] net: proc: fix build failed when procfs is not configured Gao feng
2013-02-19 10:43 ` [PATCH 2/3] net: dev: fix build failed when procfs is disabled Gao feng
2013-02-19 12:02 ` Cong Wang [this message]
2013-02-19 10:43 ` [PATCH 3/3] net: ipv4: fix waring -Wunused-variable Gao feng
2013-02-19 18:19 ` David Miller
2013-02-19 18:19 ` [PATCH 1/3] net: proc: fix build failed when procfs is not configured 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=512369EB.7090209@gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=davem@davemloft.net \
--cc=gaofeng@cn.fujitsu.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).