From: Andy Gospodarek <andy@greyhouse.net>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev@vger.kernel.org, Jay Vosburgh <j.vosburgh@gmail.com>,
Veaceslav Falico <vfalico@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jiri Pirko <jiri@resnulli.us>, Hangbin Liu <liuhangbin@gmail.com>,
Richard Cochran <richardcochran@gmail.com>,
Davide Caratti <dcaratti@redhat.com>,
Debabrata Banerjee <dbanerje@akamai.com>,
Sun Lianwen <sunlw.fnst@cn.fujitsu.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 2/2] net: Remove switchdev.h inclusion from team/bond/vlan
Date: Fri, 22 Feb 2019 15:47:30 -0500 [thread overview]
Message-ID: <20190222204730.GA73924@C02RW35GFVH8.dhcp.broadcom.net> (raw)
In-Reply-To: <20190222203134.19508-3-f.fainelli@gmail.com>
On Fri, Feb 22, 2019 at 12:31:34PM -0800, Florian Fainelli wrote:
> This is no longer necessary after eca59f691566 ("net: Remove support for bridge bypass ndos from stacked devices")
>
> Suggested-by: Ido Schimmel <idosch@mellanox.com>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Reviewed-by: Andy Gospodarek <andy@greyhouse.net>
> ---
> drivers/net/bonding/bond_main.c | 1 -
> drivers/net/team/team.c | 1 -
> net/8021q/vlan_dev.c | 1 -
> 3 files changed, 3 deletions(-)
>
> diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
> index 485462d3087f..a044a8032a0f 100644
> --- a/drivers/net/bonding/bond_main.c
> +++ b/drivers/net/bonding/bond_main.c
> @@ -77,7 +77,6 @@
> #include <net/pkt_sched.h>
> #include <linux/rculist.h>
> #include <net/flow_dissector.h>
> -#include <net/switchdev.h>
> #include <net/bonding.h>
> #include <net/bond_3ad.h>
> #include <net/bond_alb.h>
> diff --git a/drivers/net/team/team.c b/drivers/net/team/team.c
> index 958f1cf67282..3ff23a993668 100644
> --- a/drivers/net/team/team.c
> +++ b/drivers/net/team/team.c
> @@ -28,7 +28,6 @@
> #include <net/genetlink.h>
> #include <net/netlink.h>
> #include <net/sch_generic.h>
> -#include <net/switchdev.h>
> #include <generated/utsrelease.h>
> #include <linux/if_team.h>
>
> diff --git a/net/8021q/vlan_dev.c b/net/8021q/vlan_dev.c
> index b2d9c8f27cd7..15293c2a5dd8 100644
> --- a/net/8021q/vlan_dev.c
> +++ b/net/8021q/vlan_dev.c
> @@ -31,7 +31,6 @@
> #include <linux/ethtool.h>
> #include <linux/phy.h>
> #include <net/arp.h>
> -#include <net/switchdev.h>
>
> #include "vlan.h"
> #include "vlanproc.h"
> --
> 2.17.1
>
next prev parent reply other threads:[~2019-02-22 20:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 20:31 [PATCH net-next 0/2] net: switchdev.h inclusion removal Florian Fainelli
2019-02-22 20:31 ` [PATCH net-next 1/2] nfp: Remove switchdev.h inclusion Florian Fainelli
2019-02-22 21:20 ` Jakub Kicinski
2019-02-24 9:54 ` Jiri Pirko
2019-02-22 20:31 ` [PATCH net-next 2/2] net: Remove switchdev.h inclusion from team/bond/vlan Florian Fainelli
2019-02-22 20:47 ` Andy Gospodarek [this message]
2019-02-24 9:54 ` Jiri Pirko
2019-02-25 1:43 ` [PATCH net-next 0/2] net: switchdev.h inclusion removal 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=20190222204730.GA73924@C02RW35GFVH8.dhcp.broadcom.net \
--to=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dbanerje@akamai.com \
--cc=dcaratti@redhat.com \
--cc=f.fainelli@gmail.com \
--cc=j.vosburgh@gmail.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=sunlw.fnst@cn.fujitsu.com \
--cc=vfalico@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;
as well as URLs for NNTP newsgroup(s).