From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Jie Hai <haijie1@huawei.com>,
dev@dpdk.org, thomas@monjalon.net,
Yisen Zhuang <yisen.zhuang@huawei.com>
Cc: lihuisong@huawei.com, fengchengwen@huawei.com, huangdengdui@huawei.com
Subject: Re: [PATCH] net/hns3: remove roh devices
Date: Thu, 31 Oct 2024 05:47:13 +0000 [thread overview]
Message-ID: <e90b2366-4727-4b2a-92c2-8668ca3baa34@amd.com> (raw)
In-Reply-To: <20241026063835.15147-1-haijie1@huawei.com>
On 10/26/2024 7:38 AM, Jie Hai wrote:
> From: Dengdui Huang <huangdengdui@huawei.com>
>
> The devices added in commit 3f1436d7006c ("net/hns3: support new device")
> is no longer available, so revert it.
>
> Fixes: 3f1436d7006c ("net/hns3: support new device")
> Cc: stable@dpdk.org
>
> Signed-off-by: Dengdui Huang <huangdengdui@huawei.com>
>
Hi Jie, Can you please ack the patch to proceed?
next prev parent reply other threads:[~2024-10-31 5:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 6:38 Jie Hai
2024-10-31 5:47 ` Ferruh Yigit [this message]
2024-10-31 6:30 ` 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=e90b2366-4727-4b2a-92c2-8668ca3baa34@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=haijie1@huawei.com \
--cc=huangdengdui@huawei.com \
--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).