From: Parav Pandit <parav@mellanox.com>
To: Joe Perches <joe@perches.com>,
"dledford@redhat.com" <dledford@redhat.com>,
"sean.hefty@intel.com" <sean.hefty@intel.com>,
"hal.rosenstock@gmail.com" <hal.rosenstock@gmail.com>,
Moni Shoua <monis@mellanox.com>,
"santosh@chelsio.com" <santosh@chelsio.com>,
"ganeshgr@chelsio.com" <ganeshgr@chelsio.com>,
"manish.chopra@cavium.com" <manish.chopra@cavium.com>,
"rahul.verma@cavium.com" <rahul.verma@cavium.com>,
"Dept-GELinuxNICDev@cavium.com" <Dept-GELinuxNICDev@cavium.com>,
"harish.patil@cavium.com" <harish.patil@cavium.com>,
kys <kys@microsoft.com>,
"haiyangz@microsoft.com" <haiyangz@microsoft.com>,
"sthemmin@microsoft.com" <sthemmin@microsoft.com>,
"QLogic-Storage-Upstream@qlogic.com"
<QLogic-Storage-Upstream@qlogic.com>,
"jejb@linux.vnet.ibm.com" <jejb@linux.>
Subject: RE: [PATCH] net-next: treewide use is_vlan_dev() helper function.
Date: Sat, 4 Feb 2017 16:47:14 +0000 [thread overview]
Message-ID: <VI1PR0502MB300889FE34A841AD7C84EAE7D14E0__36990.4878353283$1486226849$gmane$org@VI1PR0502MB3008.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1486185045.22276.79.camel@perches.com>
Hi Joe,
> -----Original Message-----
> From: Joe Perches [mailto:joe@perches.com]
> On Fri, 2017-02-03 at 22:26 -0600, Parav Pandit wrote:
> > This patch makes use of is_vlan_dev() function instead of flag
> > comparison which is exactly done by is_vlan_dev() helper function.
>
> Thanks.
>
> btw: after applying this patch, there is one left
>
I am sending v1 to cover it as well.
> $ git grep -E -n "&\s*IFF_802_1Q_VLAN\b" -- "*.c"
> drivers/net/ethernet/chelsio/cxgb4/l2t.c:435: if (neigh->dev->priv_flags &
> IFF_802_1Q_VLAN)
next prev parent reply other threads:[~2017-02-04 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-04 4:26 [PATCH] net-next: treewide use is_vlan_dev() helper function Parav Pandit
2017-02-04 5:10 ` Joe Perches
2017-02-04 16:47 ` Parav Pandit [this message]
2017-02-04 16:47 ` Parav Pandit
[not found] ` <1486185045.22276.79.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2017-02-04 16:47 ` Parav Pandit
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='VI1PR0502MB300889FE34A841AD7C84EAE7D14E0__36990.4878353283$1486226849$gmane$org@VI1PR0502MB3008.eurprd05.prod.outlook.com' \
--to=parav@mellanox.com \
--cc=Dept-GELinuxNICDev@cavium.com \
--cc=QLogic-Storage-Upstream@qlogic.com \
--cc=dledford@redhat.com \
--cc=ganeshgr@chelsio.com \
--cc=haiyangz@microsoft.com \
--cc=hal.rosenstock@gmail.com \
--cc=harish.patil@cavium.com \
--cc=jejb@linux. \
--cc=joe@perches.com \
--cc=kys@microsoft.com \
--cc=manish.chopra@cavium.com \
--cc=monis@mellanox.com \
--cc=rahul.verma@cavium.com \
--cc=santosh@chelsio.com \
--cc=sean.hefty@intel.com \
--cc=sthemmin@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.