From: Feifei Wang <feifei.wang2@arm.com>
Cc: dev@dpdk.org, nd@arm.com, Feifei Wang <feifei.wang2@arm.com>
Subject: [dpdk-dev] [PATCH v4 0/3] fix bugs for examples/evnentdev
Date: Thu, 14 Jan 2021 18:30:58 +0800 [thread overview]
Message-ID: <20210114103101.738262-1-feifei.wang2@arm.com> (raw)
In-Reply-To: <20201221053454.47307-1-feifei.wang2@arm.com>
Fix some bugs for eventdev pipeline example.
v2:
1. Delete unused variable to fix build error
2. Reduce commit message length to fix coding style issues
v3:
1. Title improvement (Van Haaren)
v4:
1. fix core enabled bug
2. add info typo for main core
Feifei Wang (3):
doc: fix core enabled bug for eventdev pipeline example
examples/eventdev: add info typo for main core
examples/eventdev: move eth stop to the end
.../sample_app_ug/eventdev_pipeline.rst | 5 +-
examples/eventdev_pipeline/main.c | 78 +++++++++++--------
2 files changed, 47 insertions(+), 36 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2021-01-14 10:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 5:34 [dpdk-dev] [PATCH] examples/eventdev: move eth stop to the end Feifei Wang
2020-12-21 9:32 ` [dpdk-dev] [PATCH v2] " Feifei Wang
2020-12-21 9:56 ` [dpdk-dev] [PATCH] " Van Haaren, Harry
2020-12-22 5:31 ` [dpdk-dev] 回复: " Feifei Wang
2021-01-05 5:14 ` [dpdk-dev] [PATCH v3] examples/eventdev: refactor ethdev port stop Feifei Wang
2021-01-05 10:09 ` [dpdk-dev] [EXT] " Pavan Nikhilesh Bhagavatula
2021-01-14 6:24 ` [dpdk-dev] 回复: " Feifei Wang
2021-01-14 8:50 ` Feifei Wang
2021-01-14 10:30 ` Feifei Wang [this message]
2021-01-14 10:30 ` [dpdk-dev] [PATCH v4 1/3] doc: fix core enabled bug for eventdev pipeline example Feifei Wang
2021-01-14 10:31 ` [dpdk-dev] [PATCH v4 2/3] examples/eventdev: add info output for main core Feifei Wang
2021-01-14 10:31 ` [dpdk-dev] [PATCH v4 3/3] examples/eventdev: move eth stop to the end Feifei Wang
2021-01-25 17:51 ` [dpdk-dev] [EXT] " Pavan Nikhilesh Bhagavatula
2021-01-26 13:37 ` Jerin Jacob
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=20210114103101.738262-1-feifei.wang2@arm.com \
--to=feifei.wang2@arm.com \
--cc=dev@dpdk.org \
--cc=nd@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.