From: Andrew Rybchenko <arybchenko@solarflare.com>
To: <dev@dpdk.org>
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH] mempool/bucket: add the driver to meson build
Date: Wed, 16 May 2018 19:48:16 +0300 [thread overview]
Message-ID: <54998bab-d6c1-efa1-8d43-40aaf9d14c33@solarflare.com> (raw)
In-Reply-To: <1526488870-22040-1-git-send-email-arybchenko@solarflare.com>
On 05/16/2018 07:41 PM, Andrew Rybchenko wrote:
> Fixes: 4ed00862c81d ("mempool/bucket: implement bucket mempool manager")
>
> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
Self NACK, sorry v2 is sent to fix From: and I've just realized that
forgot to use --in-reply-to in v2
prev parent reply other threads:[~2018-05-16 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 16:41 Andrew Rybchenko
2018-05-16 16:48 ` Andrew Rybchenko [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=54998bab-d6c1-efa1-8d43-40aaf9d14c33@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=bruce.richardson@intel.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).