From: Randy Dunlap <randy.dunlap@oracle.com>
To: davem@davemloft.net, Patrick McHardy <kaber@trash.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
netdev@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [PATCH] net: Enter net/ipv6/ even if CONFIG_IPV6=n
Date: Fri, 04 Mar 2011 09:01:54 -0800 [thread overview]
Message-ID: <4D711B02.2060200@oracle.com> (raw)
In-Reply-To: <20110304093507.GG10761@canuck.infradead.org>
On 03/04/11 01:35, Thomas Graf wrote:
> exthdrs_core.c and addrconf_core.c in net/ipv6/ contain bits which
> must be made available even if IPv6 is disabled.
>
> net/ipv6/Makefile already correctly includes them if CONFIG_IPV6=n
> but net/Makefile prevents entering the subdirectory.
>
> Signed-off-by: Thomas Graf <tgraf@infradead.org>
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
Thanks.
>
> diff --git a/net/Makefile b/net/Makefile
> index a3330eb..a51d946 100644
> --- a/net/Makefile
> +++ b/net/Makefile
> @@ -19,9 +19,7 @@ obj-$(CONFIG_NETFILTER) += netfilter/
> obj-$(CONFIG_INET) += ipv4/
> obj-$(CONFIG_XFRM) += xfrm/
> obj-$(CONFIG_UNIX) += unix/
> -ifneq ($(CONFIG_IPV6),)
> -obj-y += ipv6/
> -endif
> +obj-$(CONFIG_NET) += ipv6/
> obj-$(CONFIG_PACKET) += packet/
> obj-$(CONFIG_NET_KEY) += key/
> obj-$(CONFIG_BRIDGE) += bridge/
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-03-04 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110210180525.54ec83e9.sfr@canb.auug.org.au>
2011-02-10 17:52 ` linux-next: Tree for February 10 (netfilter) Randy Dunlap
2011-02-14 7:34 ` Patrick McHardy
2011-03-03 21:54 ` Randy Dunlap
2011-03-04 9:35 ` [PATCH] net: Enter net/ipv6/ even if CONFIG_IPV6=n Thomas Graf
2011-03-04 17:01 ` Randy Dunlap [this message]
2011-03-07 20:51 ` 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=4D711B02.2060200@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--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).