From: Thomas Monjalon <thomas@monjalon.net>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org, Yongseok Koh <yskoh@mellanox.com>,
arybchenko@solarflare.com, konstantin.ananyev@intel.com,
stephen@networkplumber.org
Subject: Re: [dpdk-dev] [PATCH v2] doc: announce removal of indirect mbuf check macro
Date: Mon, 28 May 2018 02:54:31 +0200 [thread overview]
Message-ID: <7279012.auxEz77o4U@xps> (raw)
In-Reply-To: <20180525072017.6czdswbkwpoxbty5@neon>
25/05/2018 09:20, Olivier Matz:
> On Thu, May 24, 2018 at 06:20:06PM -0700, Yongseok Koh wrote:
> > Link: http://dpdk.org/ml/archives/dev/2018-April/099476.html
> >
> > Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
>
> Acked-by: Olivier Matz <olivier.matz@6wind.com>
Applied, thanks
next prev parent reply other threads:[~2018-05-28 0:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 0:53 [dpdk-dev] [PATCH] " Yongseok Koh
2018-05-25 1:20 ` [dpdk-dev] [PATCH v2] " Yongseok Koh
2018-05-25 6:34 ` Andrew Rybchenko
2018-05-25 7:20 ` Olivier Matz
2018-05-28 0:54 ` Thomas Monjalon [this message]
2018-05-27 4:36 ` Shahaf Shuler
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=7279012.auxEz77o4U@xps \
--to=thomas@monjalon.net \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=olivier.matz@6wind.com \
--cc=stephen@networkplumber.org \
--cc=yskoh@mellanox.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).