From: Stephen Hemminger <stephen@networkplumber.org>
To: Jie Hai <haijie1@huawei.com>
Cc: <dev@dpdk.org>, <thomas@monjalon.net>, <ferruh.yigit@amd.com>,
<aman.deep.singh@intel.com>, <lihuisong@huawei.com>,
<fengchengwen@huawei.com>, <huangdengdui@huawei.com>
Subject: Re: [PATCH v2 1/2] net: add ptype parse for tunnel packets
Date: Thu, 30 Jan 2025 10:26:50 -0800 [thread overview]
Message-ID: <20250130102650.23aad5ee@hermes.local> (raw)
In-Reply-To: <20250124094333.11449-2-haijie1@huawei.com>
On Fri, 24 Jan 2025 17:43:31 +0800
Jie Hai <haijie1@huawei.com> wrote:
> @@ -456,7 +550,6 @@ uint32_t rte_net_get_ptype(const struct rte_mbuf *m,
> ip6h = rte_pktmbuf_read(m, off, sizeof(*ip6h), &ip6h_copy);
> if (unlikely(ip6h == NULL))
> return pkt_type;
> -
> proto = ip6h->proto;
> hdr_lens->inner_l3_len = sizeof(*ip6h);
> off += hdr_lens->inner_l3_len;
Random whitespace change, not needed. Please cleanup and resubmit
next prev parent reply other threads:[~2025-01-30 18:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 2:46 [PATCH] app/testpmd: add ipv6 extension header parse Jie Hai
2025-01-08 17:02 ` Stephen Hemminger
2025-01-14 2:05 ` Jie Hai
2025-01-14 11:24 ` Thomas Monjalon
2025-01-24 9:43 ` [PATCH v2 0/2] parse ptype for tunnel packets Jie Hai
2025-01-24 9:43 ` [PATCH v2 1/2] net: add ptype parse " Jie Hai
2025-01-30 18:26 ` Stephen Hemminger [this message]
2025-01-24 9:43 ` [PATCH v2 2/2] app/test-pmd: use ptype API parse packets Jie Hai
2025-02-14 1:56 ` [PATCH v3 0/2] app/testpmd: add ipv6 extension header parse Jie Hai
2025-02-14 1:56 ` [PATCH v3 1/2] net: add ptype parse for tunnel packets Jie Hai
2025-02-14 16:35 ` Stephen Hemminger
2025-02-22 1:53 ` Jie Hai
2025-02-14 1:56 ` [PATCH v3 2/2] app/test-pmd: use ptype API parse packets Jie Hai
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=20250130102650.23aad5ee@hermes.local \
--to=stephen@networkplumber.org \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@amd.com \
--cc=haijie1@huawei.com \
--cc=huangdengdui@huawei.com \
--cc=lihuisong@huawei.com \
--cc=thomas@monjalon.net \
/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.