From: David Miller <davem@davemloft.net>
To: xiyou.wangcong@gmail.com
Cc: netdev@vger.kernel.org, stephen@networkplumber.org, kaber@trash.net
Subject: Re: [Patch net-next] ipv4: register igmp_notifier even when !CONFIG_PROC_FS
Date: Tue, 14 Jan 2014 15:04:18 -0800 (PST) [thread overview]
Message-ID: <20140114.150418.1635576593193924711.davem@davemloft.net> (raw)
In-Reply-To: <1389398985-16198-1-git-send-email-xiyou.wangcong@gmail.com>
From: Cong Wang <xiyou.wangcong@gmail.com>
Date: Fri, 10 Jan 2014 16:09:45 -0800
> We still need this notifier even when we don't config
> PROC_FS.
>
> It should be rare to have a kernel without PROC_FS,
> so just for completeness.
>
> Cc: Stephen Hemminger <stephen@networkplumber.org>
> Cc: David S. Miller <davem@davemloft.net>
> Cc: Patrick McHardy <kaber@trash.net>
> Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
This looks a little ugly, but I can't suggest anything better.
Applied, thanks.
prev parent reply other threads:[~2014-01-14 23:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 0:09 [Patch net-next] ipv4: register igmp_notifier even when !CONFIG_PROC_FS Cong Wang
2014-01-14 23:04 ` David Miller [this message]
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=20140114.150418.1635576593193924711.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=xiyou.wangcong@gmail.com \
/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