From: "lihuisong (C)" <lihuisong@huawei.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>,
Bruce Richardson <bruce.richardson@intel.com>, <dev@dpdk.org>
Cc: <stable@dpdk.org>
Subject: Re: [PATCH] ethdev: fix incorrect function name in comment
Date: Sat, 21 Oct 2023 12:10:11 +0800 [thread overview]
Message-ID: <ac7b3723-dba9-913b-e866-06992568579f@huawei.com> (raw)
In-Reply-To: <2e3ab350-b53e-462f-884c-29a028d3d929@amd.com>
在 2023/10/20 23:12, Ferruh Yigit 写道:
> On 10/20/2023 2:05 PM, Bruce Richardson wrote:
>> For those using the function comments as a guide, provide the name of
>> the correct callback function to use when wanting to count dropped
>> packets from the ethdev tx buffering system.
>>
>> Fixes: d6c99e62c852 ("ethdev: add buffered Tx")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
>>
> Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
correct, rte_eth_count_unsent_packet_callback is not even exist.
Acked-by: Huisong Li <lihuisong@huawei.com>
>
> .
next prev parent reply other threads:[~2023-10-21 4:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 13:05 Bruce Richardson
2023-10-20 15:12 ` Ferruh Yigit
2023-10-21 4:10 ` lihuisong (C) [this message]
2023-10-26 15:23 ` 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=ac7b3723-dba9-913b-e866-06992568579f@huawei.com \
--to=lihuisong@huawei.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=stable@dpdk.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).