From: David Miller <davem@davemloft.net>
To: sainath.grandhi@intel.com
Cc: netdev@vger.kernel.org, mahesh@bandewar.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 4/7] TAP: Abstract type of virtual interface from tap implementation
Date: Wed, 18 Jan 2017 16:27:30 -0500 (EST) [thread overview]
Message-ID: <20170118.162730.696191131996456647.davem@davemloft.net> (raw)
In-Reply-To: <1484697786-50323-5-git-send-email-sainath.grandhi@intel.com>
From: Sainath Grandhi <sainath.grandhi@intel.com>
Date: Tue, 17 Jan 2017 16:03:03 -0800
> @@ -46,22 +51,52 @@ static struct cdev macvtap_cdev;
> #define TUN_OFFLOADS (NETIF_F_HW_CSUM | NETIF_F_TSO_ECN | NETIF_F_TSO | \
> NETIF_F_TSO6 | NETIF_F_UFO)
>
> +static void macvtap_count_tx_dropped(struct tap_dev *tap)
> +{
> + struct macvlan_dev *vlan = (struct macvlan_dev *)container_of(tap, struct macvtap_dev, tap);
...
> +static void macvtap_count_rx_dropped(struct tap_dev *tap)
> +{
> + struct macvlan_dev *vlan = (struct macvlan_dev *)container_of(tap, struct macvtap_dev, tap);
...
> +static void macvtap_update_features(struct tap_dev *tap,
> + netdev_features_t features)
> +{
> + struct macvlan_dev *vlan = (struct macvlan_dev *)container_of(tap, struct macvtap_dev, tap);
These casts should be completely unnecessary, please remove them.
next prev parent reply other threads:[~2017-01-18 21:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 0:02 [PATCHv2 0/7] Refactor macvtap to re-use tap functionality by other virtual intefaces Sainath Grandhi
2017-01-18 0:03 ` [PATCHv2 1/7] TAP: Refactoring macvtap.c Sainath Grandhi
2017-01-18 0:03 ` [PATCHv2 2/7] TAP: Renaming tap related APIs, data structures, macros Sainath Grandhi
2017-01-18 0:03 ` [PATCHv2 3/7] TAP: Tap character device creation/destroy API Sainath Grandhi
2017-01-18 21:26 ` David Miller
2017-01-19 23:33 ` Grandhi, Sainath
2017-01-18 0:03 ` [PATCHv2 4/7] TAP: Abstract type of virtual interface from tap implementation Sainath Grandhi
2017-01-18 21:27 ` David Miller [this message]
2017-01-18 0:03 ` [PATCHv2 5/7] TAP: Extending tap device create/destroy APIs Sainath Grandhi
2017-01-18 1:00 ` Andy Shevchenko
2017-01-18 0:03 ` [PATCHv2 6/7] TAP: tap as an independent module Sainath Grandhi
2017-01-18 0:03 ` [PATCHv2 7/7] IPVTAP: IP-VLAN based tap driver Sainath Grandhi
2017-01-18 21:28 ` David Miller
2017-01-19 23:33 ` Grandhi, Sainath
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=20170118.162730.696191131996456647.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mahesh@bandewar.net \
--cc=netdev@vger.kernel.org \
--cc=sainath.grandhi@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;
as well as URLs for NNTP newsgroup(s).