All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chengwen Feng <fengchengwen@huawei.com>
To: <thomas@monjalon.net>, <ferruh.yigit@intel.com>,
	<skori@marvell.com>, <jerinj@marvell.com>,
	<anatoly.burakov@intel.com>, <harry.van.haaren@intel.com>,
	<stephen@networkplumber.org>
Cc: <dev@dpdk.org>, <linuxarm@openeuler.org>
Subject: [dpdk-dev] [PATCH v3 0/2] fix bugs for librte eal
Date: Wed, 5 May 2021 12:10:05 +0800	[thread overview]
Message-ID: <1620187807-40049-1-git-send-email-fengchengwen@huawei.com> (raw)
In-Reply-To: <1619663653-22771-1-git-send-email-humin29@huawei.com>

This patchset fixed some bugs for librte_eal.

v3:
* change patch's author
v2:
* set variables an unsigned type.

Chengwen Feng (2):
  eal: check mp reply result
  eal: fix service core index validity

 lib/eal/common/eal_common_options.c | 6 ++++--
 lib/eal/common/malloc_mp.c          | 4 +---
 2 files changed, 5 insertions(+), 5 deletions(-)

-- 
2.8.1


  parent reply	other threads:[~2021-05-05  4:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21  1:17 [dpdk-dev] [PATCH 0/2] fix bugs for librte eal Min Hu (Connor)
2021-04-21  1:17 ` [dpdk-dev] [PATCH 1/2] eal: check mp reply result Min Hu (Connor)
2021-04-21  1:17 ` [dpdk-dev] [PATCH 2/2] eal: fix service core index validity Min Hu (Connor)
2021-04-21  2:33   ` Stephen Hemminger
2021-04-29  2:34     ` Min Hu (Connor)
2021-04-29  2:34 ` [dpdk-dev] [PATCH v2 0/2] fix bugs for librte eal Min Hu (Connor)
2021-04-29  2:34   ` [dpdk-dev] [PATCH v2 1/2] eal: check mp reply result Min Hu (Connor)
2021-05-04 16:54     ` Thomas Monjalon
2021-04-29  2:34   ` [dpdk-dev] [PATCH v2 2/2] eal: fix service core index validity Min Hu (Connor)
2021-05-04 16:54     ` Thomas Monjalon
2021-05-05  4:10   ` Chengwen Feng [this message]
2021-05-05  4:10     ` [dpdk-dev] [PATCH v3 1/2] eal: check mp reply result Chengwen Feng
2021-05-05  4:10     ` [dpdk-dev] [PATCH v3 2/2] eal: fix service core index validity Chengwen Feng
2021-05-05 10:43       ` Van Haaren, Harry
2021-05-05 21:23         ` 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=1620187807-40049-1-git-send-email-fengchengwen@huawei.com \
    --to=fengchengwen@huawei.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=harry.van.haaren@intel.com \
    --cc=jerinj@marvell.com \
    --cc=linuxarm@openeuler.org \
    --cc=skori@marvell.com \
    --cc=stephen@networkplumber.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 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.