From: Jianfeng Tan <jianfeng.tan@intel.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, Jianfeng Tan <jianfeng.tan@intel.com>
Subject: [dpdk-dev] [PATCH v2 0/2] code clean up and fix in ipc
Date: Fri, 20 Apr 2018 15:20:10 +0000 [thread overview]
Message-ID: <1524237612-130629-1-git-send-email-jianfeng.tan@intel.com> (raw)
In-Reply-To: <1524187312-129804-1-git-send-email-jianfeng.tan@intel.com>
v2:
- Fix typo.
- Rebase on below patches:
http://dpdk.org/dev/patchwork/patch/38358/
http://dpdk.org/dev/patchwork/patch/38359/
http://dpdk.org/dev/patchwork/patch/38360/
Patch 1 is to rename some variable names for better readability.
Patch 2 is a bug fix.
Jianfeng Tan (2):
ipc: clearn up code
ipc: fix timeout not properly handled in async
lib/librte_eal/common/eal_common_proc.c | 90 +++++++++++++++++----------------
1 file changed, 46 insertions(+), 44 deletions(-)
--
2.7.4
next prev parent reply other threads:[~2018-04-20 15:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 1:21 [dpdk-dev] [PATCH " Jianfeng Tan
2018-04-20 1:21 ` [dpdk-dev] [PATCH 1/2] ipc: clearn up code Jianfeng Tan
2018-04-20 7:55 ` Burakov, Anatoly
2018-04-20 14:41 ` Tan, Jianfeng
2018-04-20 1:21 ` [dpdk-dev] [PATCH 2/2] ipc: fix timeout not properly handled in async Jianfeng Tan
2018-04-20 1:22 ` Tan, Jianfeng
2018-04-20 7:56 ` Burakov, Anatoly
2018-04-20 15:20 ` Jianfeng Tan [this message]
2018-04-20 15:20 ` [dpdk-dev] [PATCH v2 1/2] ipc: clearn up code Jianfeng Tan
2018-04-20 15:20 ` [dpdk-dev] [PATCH v2 2/2] ipc: fix timeout not properly handled in async Jianfeng Tan
2018-04-23 20:48 ` [dpdk-dev] [PATCH v2 0/2] code clean up and fix in ipc Thomas Monjalon
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=1524237612-130629-1-git-send-email-jianfeng.tan@intel.com \
--to=jianfeng.tan@intel.com \
--cc=dev@dpdk.org \
--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).