From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Graf Subject: Re: [PATCH net-next] ip_tunnel: Call ip_tunnel_core_init() from inet_init() Date: Thu, 23 Jul 2015 10:17:19 +0200 Message-ID: <20150723081719.GC22790@pox.localdomain> References: <20150723115824.071b84ff@canb.auug.org.au> <20150723080844.GB22790@pox.localdomain> <20150723.012849.1964809126719828221.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: sfr@canb.auug.org.au, netdev@vger.kernel.org, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org To: David Miller Return-path: Content-Disposition: inline In-Reply-To: <20150723.012849.1964809126719828221.davem@davemloft.net> Sender: linux-next-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On 07/23/15 at 01:28am, David Miller wrote: > From: Thomas Graf > Date: Thu, 23 Jul 2015 10:08:44 +0200 > > > Convert the module_init() to a invocation from inet_init() since > > ip_tunnel_core is part of the INET built-in. > > > > Fixes: 3093fbe7ff4 ("route: Per route IP tunnel metadata via lightweight tunnel") > > Signed-off-by: Thomas Graf > > I applied this instead of my module.h include fix, thanks Thomas. Thanks, sorry for the extra trouble you had to go through.