netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eran Ben Elisha <eranbe@nvidia.com>
To: "David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>
Cc: <netdev@vger.kernel.org>, Tariq Toukan <tariqt@nvidia.com>,
	Cong Wang <xiyou.wangcong@gmail.com>,
	Eric Dumazet <edumazet@google.com>, Jiri Pirko <jiri@nvidia.com>,
	Vladimir Oltean <vladimir.oltean@nxp.com>,
	Jakub Sitnicki <jakub@cloudflare.com>,
	Guillaume Nault <gnault@redhat.com>,
	Eran Ben Elisha <eranbe@nvidia.com>
Subject: [PATCH net-next v2 0/2] Dissect PTP L2 packet header
Date: Mon, 11 Jan 2021 11:46:50 +0200	[thread overview]
Message-ID: <1610358412-25248-1-git-send-email-eranbe@nvidia.com> (raw)

Hi Jakub, Dave,

This series adds support for dissecting PTP L2 packet
header (EtherType 0x88F7).

For packet header dissecting, skb->protocol is needed. Add protocol
parsing operation to vlan ops, to guarantee skb->protocol is set,
as EtherType 0x88F7 occasionally follows a vlan header.

Changelog:
v2:
- Add more people to CC list.

Eran Ben Elisha (2):
  net: vlan: Add parse protocol header ops
  net: flow_dissector: Parse PTP L2 packet header

 net/8021q/vlan_dev.c      |  9 +++++++++
 net/core/flow_dissector.c | 16 ++++++++++++++++
 2 files changed, 25 insertions(+)

-- 
2.17.1


             reply	other threads:[~2021-01-11  9:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11  9:46 Eran Ben Elisha [this message]
2021-01-11  9:46 ` [PATCH net-next v2 1/2] net: vlan: Add parse protocol header ops Eran Ben Elisha
2021-01-11  9:46 ` [PATCH net-next v2 2/2] net: flow_dissector: Parse PTP L2 packet header Eran Ben Elisha
2021-01-11 15:49 ` [PATCH net-next v2 0/2] Dissect " Andrew Lunn
2021-01-11 18:14   ` Eran Ben Elisha

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=1610358412-25248-1-git-send-email-eranbe@nvidia.com \
    --to=eranbe@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gnault@redhat.com \
    --cc=jakub@cloudflare.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tariqt@nvidia.com \
    --cc=vladimir.oltean@nxp.com \
    --cc=xiyou.wangcong@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).