From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yongseok Koh <yskoh@mellanox.com>, shahafs@mellanox.com
Cc: dev@dpdk.org, thomas@monjalon.net, stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] doc: fix typo in mlx5 guide
Date: Wed, 8 May 2019 20:20:25 +0100 [thread overview]
Message-ID: <970a0564-f78f-0817-95c3-1f7219431048@intel.com> (raw)
In-Reply-To: <20190508092409.11861-1-yskoh@mellanox.com>
On 5/8/2019 10:24 AM, Yongseok Koh wrote:
> Fixes: 43e9d9794cde ("net/mlx5: support upstream rdma-core")
> Cc: stable@dpdk.org
>
> Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-05-08 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 9:24 [dpdk-dev] " Yongseok Koh
2019-05-08 9:24 ` Yongseok Koh
2019-05-08 19:20 ` Ferruh Yigit [this message]
2019-05-08 19:20 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
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=970a0564-f78f-0817-95c3-1f7219431048@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=shahafs@mellanox.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--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).