netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matteo Croce <mcroce@redhat.com>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>,
	Mahesh Bandewar <maheshb@google.com>,
	Florian Westphal <fw@strlen.de>
Subject: [PATCH v2 net-next 2/2] ipvlan: selects master_l3 device instead of depending on it
Date: Sat, 17 Feb 2018 20:11:50 +0100	[thread overview]
Message-ID: <20180217191150.7643-3-mcroce@redhat.com> (raw)
In-Reply-To: <20180217191150.7643-1-mcroce@redhat.com>

The L3 Master device is just a glue between the core networking code and
device drivers, so it should be selected automatically rather than
requiring to be enabled explicitly.

Signed-off-by: Matteo Croce <mcroce@redhat.com>
---
 drivers/net/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
index 3234c6618d75..d88b78a17440 100644
--- a/drivers/net/Kconfig
+++ b/drivers/net/Kconfig
@@ -150,7 +150,7 @@ config IPVLAN
     tristate "IP-VLAN support"
     depends on INET
     depends on NETFILTER
-    depends on NET_L3_MASTER_DEV
+    select NET_L3_MASTER_DEV
     ---help---
       This allows one to create virtual devices off of a main interface
       and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
-- 
2.14.3

  parent reply	other threads:[~2018-02-17 19:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-17 19:11 [PATCH v2 net-next 0/3] Remove IPVlan module dependencies on IPv6 and L3 Master dev Matteo Croce
2018-02-17 19:11 ` [PATCH v2 net-next 1/2] ipvlan: drop ipv6 dependency Matteo Croce
2018-02-19 10:33   ` [PATCH v3 " Matteo Croce
2018-02-19 14:58     ` David Miller
2018-02-17 19:11 ` Matteo Croce [this message]
2018-02-17 19:21 ` [PATCH v2 net-next 0/3] Remove IPVlan module dependencies on IPv6 and L3 Master dev Matteo Croce

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=20180217191150.7643-3-mcroce@redhat.com \
    --to=mcroce@redhat.com \
    --cc=davem@davemloft.net \
    --cc=fw@strlen.de \
    --cc=maheshb@google.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).