patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Bruce Richardson" <bruce.richardson@intel.com>, <dev@dpdk.org>
Cc: <david.marchand@redhat.com>, <probb@iol.unh.edu>, <stable@dpdk.org>
Subject: RE: [PATCH v6 01/11] mempool: fix default ops for an empty mempool
Date: Wed, 16 Aug 2023 18:32:07 +0200	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D87B0C@smartserver.smartshare.dk> (raw)
In-Reply-To: <20230816153439.551501-2-bruce.richardson@intel.com>

> From: Bruce Richardson [mailto:bruce.richardson@intel.com]
> Sent: Wednesday, 16 August 2023 17.34
> 
> From: David Marchand <david.marchand@redhat.com>
> 
> An empty mempool's ops were not initialised to a default value wrt to
> what the application requested via the flags parameter.  As
> rte_mempool_create() relies on rte_mempool_create_empty(), simply move
> this ops initialisation to rte_mempool_create_empty().
> 
> Fixes: aa10457eb4c2 ("mempool: make mempool populate and free api
> public")
> Cc: stable@dpdk.org
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> Reviewed-by: Bruce Richardson <bruce.richardson@intel.com>
> ---

I would have moved it to the exact same location.

Reviewed-by: Morten Brørup <mb@smartsharesystems.com>


      reply	other threads:[~2023-08-16 16:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230721115125.55137-1-bruce.richardson@intel.com>
     [not found] ` <20230816153439.551501-1-bruce.richardson@intel.com>
2023-08-16 15:34   ` Bruce Richardson
2023-08-16 16:32     ` Morten Brørup [this message]

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=98CBD80474FA8B44BF855DF32C47DC35D87B0C@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=probb@iol.unh.edu \
    --cc=stable@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).