public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
To: netdev@vger.kernel.org
Cc: Claudiu Manoil <claudiu.manoil@nxp.com>,
	Faisal Latif <faisal.latif@intel.com>,
	Pravin B Shelar <pshelar@ovn.org>,
	Shiraz Saleem <shiraz.saleem@intel.com>,
	dev@openvswitch.org, linux-rdma@vger.kernel.org
Subject: [PATCH net-next 0/4] Remove VLAN_TAG_PRESENT from drivers
Date: Thu, 08 Nov 2018 18:44:46 +0100	[thread overview]
Message-ID: <cover.1541698641.git.mirq-linux@rere.qmqm.pl> (raw)

This series removes VLAN_TAG_PRESENT use from network drivers in
preparation to removing its special meaning.

Michał Mirosław (4):
  i40iw: remove use of VLAN_TAG_PRESENT
  cnic: remove use of VLAN_TAG_PRESENT
  gianfar: remove use of VLAN_TAG_PRESENT
  OVS: remove use of VLAN_TAG_PRESENT

 drivers/infiniband/hw/i40iw/i40iw_cm.c        |  8 +++----
 drivers/net/ethernet/broadcom/cnic.c          |  2 +-
 .../net/ethernet/freescale/gianfar_ethtool.c  |  8 +++----
 net/openvswitch/actions.c                     | 13 +++++++----
 net/openvswitch/flow.c                        |  4 ++--
 net/openvswitch/flow.h                        |  2 +-
 net/openvswitch/flow_netlink.c                | 22 +++++++++----------
 7 files changed, 31 insertions(+), 28 deletions(-)

-- 
2.19.1

             reply	other threads:[~2018-11-08 17:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 17:44 Michał Mirosław [this message]
2018-11-08 17:44 ` [PATCH net-next] i40iw: remove use of VLAN_TAG_PRESENT Michał Mirosław
2018-11-08 17:44 ` [PATCH net-next 2/4] cnic: " Michał Mirosław
2018-11-08 17:44 ` [PATCH net-next 4/4] OVS: " Michał Mirosław
2018-11-08 17:44 ` [PATCH net-next 3/4] gianfar: " Michał Mirosław
     [not found] ` <cover.1541698641.git.mirq-linux-CoA6ZxLDdyEEUmgCuDUIdw@public.gmane.org>
2018-11-08 18:50   ` [PATCH net-next 0/4] Remove VLAN_TAG_PRESENT from drivers Leon Romanovsky
2018-11-08 22:11     ` Michał Mirosław
2018-11-09  3:49 ` David Miller
2018-11-09 21:58 ` Shiraz Saleem

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=cover.1541698641.git.mirq-linux@rere.qmqm.pl \
    --to=mirq-linux@rere.qmqm.pl \
    --cc=claudiu.manoil@nxp.com \
    --cc=dev@openvswitch.org \
    --cc=faisal.latif@intel.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@ovn.org \
    --cc=shiraz.saleem@intel.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