From: John Crispin <john@phrozen.org>
To: Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S . Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
John Crispin <john@phrozen.org>
Subject: [PATCH V2 2/4] net-next: dsa: add 802.3 protocol offset to struct dsa_device_ops
Date: Fri, 21 Jul 2017 10:58:11 +0200 [thread overview]
Message-ID: <20170721085813.30789-2-john@phrozen.org> (raw)
In-Reply-To: <20170721085813.30789-1-john@phrozen.org>
Adding these 2 new fields allows a DSA device to indicate the offsets of
the 802.3 header caused by the insertion of the switches tag.
Signed-off-by: John Crispin <john@phrozen.org>
---
include/net/dsa.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/include/net/dsa.h b/include/net/dsa.h
index a4c0d52abc80..b98bc3621905 100644
--- a/include/net/dsa.h
+++ b/include/net/dsa.h
@@ -106,6 +106,11 @@ struct dsa_device_ops {
struct sk_buff *(*rcv)(struct sk_buff *skb, struct net_device *dev,
struct packet_type *pt,
struct net_device *orig_dev);
+ /*
+ * Network header and 802.3 protocol offsets
+ */
+ int hash_nh_off;
+ int hash_proto_off;
};
struct dsa_switch_tree {
--
2.11.0
next prev parent reply other threads:[~2017-07-21 8:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 8:58 [PATCH V2 1/4] net-next: dsa: move struct dsa_device_ops to the global header file John Crispin
2017-07-21 8:58 ` John Crispin [this message]
2017-07-21 8:58 ` [PATCH V2 3/4] net-next: dsa: fix flow dissection John Crispin
2017-07-23 20:26 ` kbuild test robot
2017-07-26 15:10 ` Andrew Lunn
2017-07-28 19:40 ` John Crispin
2017-07-28 21:25 ` Andrew Lunn
2017-07-21 8:58 ` [PATCH V2 4/4] net-next: tag_mtk: add nh and proto offsets to the ops struct John Crispin
2017-07-21 19:12 ` [PATCH V2 1/4] net-next: dsa: move struct dsa_device_ops to the global header file David Miller
2017-07-26 14:53 ` Andrew Lunn
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=20170721085813.30789-2-john@phrozen.org \
--to=john@phrozen.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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.