DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Jie Hai <haijie1@huawei.com>,
	dev@dpdk.org, Yisen Zhuang <yisen.zhuang@huawei.com>
Cc: lihuisong@huawei.com, fengchengwen@huawei.com,
	thomas@monjalon.net, ivan.malov@arknetworks.am
Subject: Re: [PATCH] net/hns3: support more VLAN fields matching
Date: Sun, 7 Jul 2024 23:44:05 +0100	[thread overview]
Message-ID: <b36aad23-7d29-46c6-a676-30b627df5ad4@amd.com> (raw)
In-Reply-To: <20240704021538.836403-1-haijie1@huawei.com>

On 7/4/2024 3:15 AM, Jie Hai wrote:
> The commit 09315fc83861 ("ethdev: add VLAN attributes to ethernet
> and VLAN items") introduces ``has_vlan`` and ``has_more_vlan``
> fields in items ETH and VLAN. This patch adds support for these
> fields. The usage is documented in hns3.rst.
> 
> Signed-off-by: Jie Hai <haijie1@huawei.com>
>

Applied to dpdk-next-net/main, thanks.

      reply	other threads:[~2024-07-07 22:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04  2:15 Jie Hai
2024-07-07 22:44 ` Ferruh Yigit [this message]

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=b36aad23-7d29-46c6-a676-30b627df5ad4@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=haijie1@huawei.com \
    --cc=ivan.malov@arknetworks.am \
    --cc=lihuisong@huawei.com \
    --cc=thomas@monjalon.net \
    --cc=yisen.zhuang@huawei.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).