From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Thomas F Herbert <thomasfherbert@gmail.com>,
netdev@vger.kernel.org, pshelar@nicira.com
Subject: Re: [PATCH net-next V16 2/3] Check for vlan ethernet types for 8021.q or 802.1ad
Date: Thu, 15 Oct 2015 20:19:11 +0300 [thread overview]
Message-ID: <561FE00F.2030207@cogentembedded.com> (raw)
In-Reply-To: <1444919813-27880-1-git-send-email-thomasfherbert@gmail.com>
On 10/15/2015 05:36 PM, Thomas F Herbert wrote:
> Signed-off-by: Thomas F Herbert <thomasfherbert@gmail.com>
> ---
> include/linux/if_vlan.h | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/include/linux/if_vlan.h b/include/linux/if_vlan.h
> index 67ce5bd..ac23521 100644
> --- a/include/linux/if_vlan.h
> +++ b/include/linux/if_vlan.h
> @@ -627,6 +627,22 @@ static inline netdev_features_t vlan_features_check(const struct sk_buff *skb,
>
> return features;
> }
> +/**
> + * eth_type_vlan - check for valid vlan ether type.
> + * @ethertype: ether type to check
> + *
> + * Returns true if the ether type is a vlan ether type.
> + */
> +static inline bool eth_type_vlan(__be16 ethertype)
> +{
> + switch (ethertype) {
> + case (htons(ETH_P_8021Q)):
> + case (htons(ETH_P_8021AD)):
Nothing changed here. :-(
[...]
MBR, Sergei
next prev parent reply other threads:[~2015-10-15 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 14:36 [PATCH net-next V16 2/3] Check for vlan ethernet types for 8021.q or 802.1ad Thomas F Herbert
2015-10-15 17:19 ` Sergei Shtylyov [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-15 14:01 [PATCH net-next V16 0/3] openvswitch: Add support for 802.1ad Thomas F Herbert
2015-10-15 14:01 ` [PATCH net-next V16 2/3] Check for vlan ethernet types for 8021.q or 802.1ad Thomas F Herbert
2015-10-15 14:05 ` Sergei Shtylyov
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=561FE00F.2030207@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--cc=thomasfherbert@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).