From: Alan Elder <alan.elder@microsoft.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>,
Long Li <longli@microsoft.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: "dev@dpdk.org" <dev@dpdk.org>, stephen <stephen@networkplumber.org>
Subject: [PATCH v7 0/2] fix parsing of VLAN metadata
Date: Mon, 19 Feb 2024 09:31:08 +0000 [thread overview]
Message-ID: <PA4PR83MB05261D63539878BF685FA37B97512@PA4PR83MB0526.EURPRD83.prod.outlook.com> (raw)
In-Reply-To: <8139ddff-aabf-4ee0-a51b-a2a658691624@amd.com>
The previous netvsc code incorrectly parsed the VLAN ID and priority.
If the 16-bits of VLAN ID and priority/CFI on the wire was
0123456789ABCDEF the code parsed it as 456789ABCDEF3012. This patch
fixes netvsc parsing code and adds common macros for extracting and
setting parts of the VLAN tag.
Alan Elder (2):
lib/net: fix parsing of VLAN metadata
net/netvsc: fix parsing of VLAN metadata
---
v7:
* Split patches for lib and driver
v6:
* Line length can be 100 - un-split lines
v5:
* Move the VLAN parsing macros to rte_ether.h
v4:
* Make consistent with FreeBSD code
---
.mailmap | 1 +
drivers/net/netvsc/hn_rxtx.c | 8 ++++++--
lib/net/rte_ether.h | 14 ++++++++++++++
3 files changed, 21 insertions(+), 2 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2024-02-19 9:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 15:09 [PATCH v3] net/netvsc: " Alan Elder
2024-02-09 1:18 ` Long Li
2024-02-09 15:50 ` [PATCH v4] " Alan Elder
2024-02-14 22:17 ` Long Li
2024-02-15 11:46 ` Ferruh Yigit
2024-02-15 18:12 ` [PATCH v5] " Alan Elder
2024-02-15 18:25 ` Stephen Hemminger
2024-02-16 9:43 ` [PATCH v6] " Alan Elder
2024-02-16 11:39 ` Ferruh Yigit
2024-02-19 9:31 ` Alan Elder [this message]
2024-02-19 9:31 ` [PATCH v7 1/2] lib/net: " Alan Elder
2024-02-19 11:12 ` Ferruh Yigit
2024-02-19 11:14 ` Ferruh Yigit
2024-02-19 9:31 ` [PATCH v7 2/2] net/netvsc: " Alan Elder
2024-02-19 11:12 ` Ferruh Yigit
2024-02-19 9:34 ` [EXTERNAL] Re: [PATCH v6] " Alan Elder
2024-02-16 11:33 ` [PATCH v5] " Ferruh Yigit
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=PA4PR83MB05261D63539878BF685FA37B97512@PA4PR83MB0526.EURPRD83.prod.outlook.com \
--to=alan.elder@microsoft.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=longli@microsoft.com \
--cc=stephen@networkplumber.org \
/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).