From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Jie Hai <haijie1@huawei.com>,
thomas@monjalon.net, dev@dpdk.org, andrew.rybchenko@oktetlabs.ru
Cc: fengchengwen@huawei.com, lihuisong@huawei.com
Subject: Re: [PATCH v2 0/2] app/testpmd: support set RSS hash algorithm
Date: Mon, 4 Dec 2023 13:57:32 +0000 [thread overview]
Message-ID: <442062ed-9964-4605-8b83-a36bb54b3499@amd.com> (raw)
In-Reply-To: <20231201085254.1545584-1-haijie1@huawei.com>
On 12/1/2023 8:52 AM, Jie Hai wrote:
> This patch set supports setting RSS hash algorithm.
>
> --
> v2:
> 1. fix misspelling and format.
> 2. fix CI compile error.
> 3. add reviewed-by for patch 1.
> --
>
> Jie Hai (2):
> ethdev: add new API to get RSS hash algorithm by name
> app/testpmd: support set RSS hash algorithm
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-12-04 13:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 9:48 [PATCH " Jie Hai
2023-11-22 9:48 ` [PATCH 1/2] ethdev: add new API to get RSS hash algorithm by name Jie Hai
2023-11-22 9:48 ` [PATCH 2/2] app/testpmd: support set RSS hash algorithm Jie Hai
2023-11-22 10:46 ` [PATCH 0/2] " Ferruh Yigit
2023-11-23 6:32 ` Jie Hai
2023-11-30 9:02 ` Ferruh Yigit
2023-11-30 10:01 ` Jie Hai
2023-11-30 10:44 ` [RESEND " Jie Hai
2023-11-30 10:44 ` [RESEND 1/2] ethdev: add new API to get RSS hash algorithm by name Jie Hai
2023-11-30 11:23 ` Ferruh Yigit
2023-11-30 10:44 ` [RESEND 2/2] app/testpmd: support set RSS hash algorithm Jie Hai
2023-11-30 11:37 ` Ferruh Yigit
2023-11-30 11:38 ` Ferruh Yigit
2023-12-01 8:52 ` [PATCH v2 0/2] " Jie Hai
2023-12-01 8:52 ` [PATCH v2 1/2] ethdev: add new API to get RSS hash algorithm by name Jie Hai
2023-12-01 8:52 ` [PATCH v2 2/2] app/testpmd: support set RSS hash algorithm Jie Hai
2023-12-01 11:26 ` Ferruh Yigit
2023-12-04 13:57 ` 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=442062ed-9964-4605-8b83-a36bb54b3499@amd.com \
--to=ferruh.yigit@amd.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=haijie1@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 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).