From: fengchengwen <fengchengwen@huawei.com>
To: Fengnan Chang <changfengnan@bytedance.com>,
<david.marchand@redhat.com>, <anatoly.burakov@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v3] eal: fix prompt info when remap_segment failed
Date: Wed, 5 Jul 2023 09:33:22 +0800 [thread overview]
Message-ID: <2c4141ee-1a38-9290-fe82-85069b49900d@huawei.com> (raw)
In-Reply-To: <20230704121751.92253-1-changfengnan@bytedance.com>
This is bugfix, suggest add Cc.
With above add, Acked-by: Chengwen Feng <fengchengwen@huawei.com>
On 2023/7/4 20:17, Fengnan Chang wrote:
> When there is not enough space to memsegs, we should prompt
> which configuration should be modified instead of printing
> some numbers.
>
> Signed-off-by: Fengnan Chang <changfengnan@bytedance.com>
> ---
> lib/eal/common/eal_common_dynmem.c | 6 ++----
> lib/eal/freebsd/eal_memory.c | 8 +++-----
> lib/eal/linux/eal_memory.c | 11 ++++-------
> 3 files changed, 9 insertions(+), 16 deletions(-)
>
...
next prev parent reply other threads:[~2023-07-05 1:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 12:17 Fengnan Chang
2023-07-04 12:43 ` Burakov, Anatoly
2023-07-05 1:33 ` fengchengwen [this message]
2023-07-06 14:16 ` 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=2c4141ee-1a38-9290-fe82-85069b49900d@huawei.com \
--to=fengchengwen@huawei.com \
--cc=anatoly.burakov@intel.com \
--cc=changfengnan@bytedance.com \
--cc=david.marchand@redhat.com \
--cc=dev@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).