From: David Miller <davem@davemloft.net>
To: tgraf@suug.ch
Cc: sfr@canb.auug.org.au, netdev@vger.kernel.org,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] ip_tunnel: Call ip_tunnel_core_init() from inet_init()
Date: Thu, 23 Jul 2015 01:28:49 -0700 (PDT) [thread overview]
Message-ID: <20150723.012849.1964809126719828221.davem@davemloft.net> (raw)
In-Reply-To: <20150723080844.GB22790@pox.localdomain>
From: Thomas Graf <tgraf@suug.ch>
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 <tgraf@suug.ch>
I applied this instead of my module.h include fix, thanks Thomas.
next prev parent reply other threads:[~2015-07-23 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 1:58 linux-next: build failure after merge of the net-next tree Stephen Rothwell
2015-07-23 8:08 ` [PATCH net-next] ip_tunnel: Call ip_tunnel_core_init() from inet_init() Thomas Graf
2015-07-23 8:28 ` David Miller [this message]
2015-07-23 8:17 ` Thomas Graf
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=20150723.012849.1964809126719828221.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tgraf@suug.ch \
/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).