From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org
Cc: ferruh.yigit@intel.com, david.marchand@redhat.com,
bruce.richardson@intel.com, olivier.matz@6wind.com,
ciara.power@intel.com, akhil.goyal@nxp.com,
fiona.trahe@intel.com, john.griffin@intel.com,
deepak.k.jain@intel.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/5] mem: fix config name in error logs
Date: Wed, 28 Oct 2020 12:08:56 +0000 [thread overview]
Message-ID: <44ed932e-c649-2b0e-e974-64d092aa1a37@intel.com> (raw)
In-Reply-To: <20201022220525.1532249-3-thomas@monjalon.net>
On 22-Oct-20 11:05 PM, Thomas Monjalon wrote:
> When introducing the new option CONFIG_RTE_MAX_MEM_MB_PER_TYPE,
> some logs were referencing a wrong name: CONFIG_RTE_MAX_MEM_PER_TYPE.
>
> Fixes: 66cc45e293ed ("mem: replace memseg with memseg lists")
> Cc: stable@dpdk.org
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2020-10-28 12:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 22:05 [dpdk-dev] [PATCH 0/5] cleanup comments and logs about config options Thomas Monjalon
2020-10-22 22:05 ` [dpdk-dev] [PATCH 1/5] eal: remove comment about old partition option Thomas Monjalon
2020-10-28 12:08 ` Burakov, Anatoly
2020-10-22 22:05 ` [dpdk-dev] [PATCH 2/5] mem: fix config name in error logs Thomas Monjalon
2020-10-28 12:08 ` Burakov, Anatoly [this message]
2020-10-22 22:05 ` [dpdk-dev] [PATCH 3/5] lib: remove config prefix used with make Thomas Monjalon
2020-10-23 6:28 ` Ruifeng Wang
2020-10-22 22:05 ` [dpdk-dev] [PATCH 4/5] drivers: " Thomas Monjalon
2020-10-22 22:10 ` Ajit Khaparde
2020-10-23 1:55 ` Wang, Haiyue
2020-10-23 6:47 ` Andrew Rybchenko
2020-10-22 22:05 ` [dpdk-dev] [PATCH 5/5] doc: remove references to make from known issues Thomas Monjalon
2020-10-23 7:37 ` [dpdk-dev] [PATCH 0/5] cleanup comments and logs about config options David Marchand
2020-10-23 17:24 ` 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=44ed932e-c649-2b0e-e974-64d092aa1a37@intel.com \
--to=anatoly.burakov@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=bruce.richardson@intel.com \
--cc=ciara.power@intel.com \
--cc=david.marchand@redhat.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@intel.com \
--cc=john.griffin@intel.com \
--cc=olivier.matz@6wind.com \
--cc=stable@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).