From: Thomas Monjalon <thomas@monjalon.net>
To: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
Cc: dev@dpdk.org, olivier.matz@6wind.com, andrew.rybchenko@oktetlabs.ru
Subject: Re: [PATCH 0/2] common/mlx5: fix multi-process mempool registration
Date: Mon, 10 Oct 2022 15:20:06 +0200 [thread overview]
Message-ID: <2763339.AiC22s8V5E@thomas> (raw)
In-Reply-To: <20220808094236.3395516-1-dkozlyuk@nvidia.com>
08/08/2022 11:42, Dmitry Kozlyuk:
> Dmitry Kozlyuk (2):
> mempool: make event callbacks process-private
> common/mlx5: fix multi-process mempool registration
Applied, thanks.
prev parent reply other threads:[~2022-10-10 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 9:42 Dmitry Kozlyuk
2022-08-08 9:42 ` [PATCH 1/2] mempool: make event callbacks process-private Dmitry Kozlyuk
2022-08-28 18:33 ` Slava Ovsiienko
2022-10-10 8:02 ` Andrew Rybchenko
2022-09-22 7:31 ` Dmitry Kozlyuk
2022-08-08 9:42 ` [PATCH 2/2] common/mlx5: fix multi-process mempool registration Dmitry Kozlyuk
2022-08-28 18:34 ` Slava Ovsiienko
2022-10-10 13:20 ` Thomas Monjalon [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=2763339.AiC22s8V5E@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=dkozlyuk@nvidia.com \
--cc=olivier.matz@6wind.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).