From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Haiyue Wang <haiyue.wang@intel.com>, dev@dpdk.org
Cc: stable@dpdk.org, Olivier MATZ <olivier.matz@6wind.com>
Subject: Re: [dpdk-stable] [PATCH v1] mbuf: fix RTE_ETH_IS_IPV6_HDR comment typo
Date: Fri, 15 Jun 2018 16:06:03 +0100 [thread overview]
Message-ID: <dd31419b-e93b-4e1d-8d0f-2dc791492222@intel.com> (raw)
In-Reply-To: <d6d593e8-54ab-dd46-825d-5cfd626ed194@intel.com>
On 6/14/2018 5:45 PM, Ferruh Yigit wrote:
> On 6/14/2018 4:09 AM, Haiyue Wang wrote:
>> It should be IPv6, not IPv4.
>>
Fixes: f295a00a2b44 ("mbuf: add definitions of unified packet types")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-06-15 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 3:09 Haiyue Wang
2018-06-14 16:45 ` Ferruh Yigit
2018-06-15 15:06 ` Ferruh Yigit [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=dd31419b-e93b-4e1d-8d0f-2dc791492222@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=olivier.matz@6wind.com \
--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).