From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>, <olivier.matz@6wind.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] mempool: check for invalid args on creation
Date: Thu, 2 Aug 2018 14:10:43 +0300 [thread overview]
Message-ID: <33a1d258-7331-e7b1-3694-e784d46006b9@solarflare.com> (raw)
In-Reply-To: <20180802003504.30679-1-pablo.de.lara.guarch@intel.com>
On 02.08.2018 03:35, Pablo de Lara wrote:
> Currently, a mempool can be created if the number of
> objects is zero. However, in this scenario,
> rte_mempool_create should return NULL,
> as the mempool created is useless otherwise.
>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
next prev parent reply other threads:[~2018-08-02 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 10:37 [dpdk-dev] [PATCH] " Pablo de Lara
2018-07-20 15:49 ` Andrew Rybchenko
2018-08-01 18:16 ` De Lara Guarch, Pablo
2018-08-02 7:15 ` Andrew Rybchenko
2018-08-02 0:35 ` [dpdk-dev] [PATCH v2] " Pablo de Lara
2018-08-02 11:10 ` Andrew Rybchenko [this message]
2018-08-05 13:35 ` 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=33a1d258-7331-e7b1-3694-e784d46006b9@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=pablo.de.lara.guarch@intel.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 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).