From: "Hunt, David" <david.hunt@intel.com>
To: Xiao Wang <xiao.w.wang@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/2] l3fwd-power: fix a typo
Date: Fri, 14 Feb 2020 10:46:45 +0000 [thread overview]
Message-ID: <06a28cd1-075e-aba5-e76d-2b58d4d8bebb@intel.com> (raw)
In-Reply-To: <20200121030657.39048-2-xiao.w.wang@intel.com>
On 21/1/2020 3:06 AM, Xiao Wang wrote:
> Fixes: aee3bc79cc34 ("examples/l3fwd-power: enable one-shot Rx interrupt and polling switch")
> Cc: stable@dpdk.org
>
> Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>
> ---
> examples/l3fwd-power/main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/examples/l3fwd-power/main.c b/examples/l3fwd-power/main.c
> index d049d8a5d..ffcc7ecf4 100644
> --- a/examples/l3fwd-power/main.c
> +++ b/examples/l3fwd-power/main.c
> @@ -1338,7 +1338,7 @@ main_loop(__attribute__((unused)) void *dummy)
> */
> rte_delay_us(lcore_idle_hint);
> else {
> - /* suspend until rx interrupt trigges */
> + /* suspend until rx interrupt triggers */
> if (intr_en) {
> turn_on_intr(qconf);
> sleep_until_rx_interrupt(
Acked-by: David Hunt <david.hunt@intel.com>
next prev parent reply other threads:[~2020-02-14 10:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 3:06 [dpdk-dev] [PATCH 0/2] l3fwd-power fixes Xiao Wang
2020-01-21 3:06 ` [dpdk-dev] [PATCH 1/2] l3fwd-power: fix a typo Xiao Wang
2020-02-14 10:46 ` Hunt, David
2020-02-14 10:46 ` Hunt, David [this message]
2020-01-21 3:06 ` [dpdk-dev] [PATCH 2/2] l3fwd-power: fix interrupt disable Xiao Wang
2020-01-22 13:30 ` Harman Kalra
2020-01-22 14:32 ` Wang, Xiao W
2020-01-23 17:42 ` [dpdk-dev] [EXT] " Harman Kalra
2020-01-30 17:40 ` [dpdk-dev] " Liang, Ma
2020-02-14 10:43 ` Hunt, David
2020-02-05 17:25 ` Liang, Ma
2020-02-14 12:46 ` [dpdk-dev] [PATCH 0/2] l3fwd-power fixes David Marchand
-- strict thread matches above, loose matches on Subject: below --
2020-01-03 18:39 [dpdk-dev] [PATCH 1/2] l3fwd-power: fix a typo Xiao Wang
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=06a28cd1-075e-aba5-e76d-2b58d4d8bebb@intel.com \
--to=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=xiao.w.wang@intel.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).