From: Thomas Monjalon <thomas@monjalon.net>
To: Michael Pfeiffer <michael.pfeiffer@tu-ilmenau.de>,
Olivier Matz <olivier.matz@6wind.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Wenzhuo Lu <wenzhuo.lu@intel.com>,
Beilei Xing <beilei.xing@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>,
Ziyang Xuan <xuanziyang2@huawei.com>,
Xiaoyun Wang <cloud.wangxiaoyun@huawei.com>,
Guoyang Zhou <zhouguoyang@huawei.com>,
Keith Wiles <keith.wiles@intel.com>,
Yong Wang <yongwang@vmware.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Chenbo Xia <chenbo.xia@intel.com>,
Zhihong Wang <zhihong.wang@intel.com>,
dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net: add rte_ipv4_hdr_len()
Date: Tue, 13 Oct 2020 19:55:25 +0200 [thread overview]
Message-ID: <8219707.uq3zTIkvgX@thomas> (raw)
In-Reply-To: <fc6964d3-d28f-042e-1f81-c13c4aaded12@intel.com>
13/10/2020 19:40, Ferruh Yigit:
> On 10/12/2020 3:55 PM, Michael Pfeiffer wrote:
> > Add a function to calculate the length of an IPv4 header as suggested
> > on the mailing list [1]. Call where appropriate.
> >
> > [1] https://mails.dpdk.org/archives/dev/2020-October/184471.html
> >
> > Suggested-by: Thomas Monjalon <thomas@monjalon.net>
> > Signed-off-by: Michael Pfeiffer <michael.pfeiffer@tu-ilmenau.de>
>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Applied to dpdk-next-net/main, thanks.
> Updated patch title to "net: add function to calculate IPv4 header length"
>
>
> Since you are already on it, a similar function to get the version also can be
> useful, if you have time for it.
Ah ah, we keep asking more to Michael :)
Hope you enjoy the ride Michael, otherwise feel free to say no.
prev parent reply other threads:[~2020-10-13 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 14:55 Michael Pfeiffer
2020-10-13 17:40 ` Ferruh Yigit
2020-10-13 17:55 ` 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=8219707.uq3zTIkvgX@thomas \
--to=thomas@monjalon.net \
--cc=beilei.xing@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=chenbo.xia@intel.com \
--cc=cloud.wangxiaoyun@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=keith.wiles@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=michael.pfeiffer@tu-ilmenau.de \
--cc=olivier.matz@6wind.com \
--cc=wenzhuo.lu@intel.com \
--cc=xuanziyang2@huawei.com \
--cc=yongwang@vmware.com \
--cc=zhihong.wang@intel.com \
--cc=zhouguoyang@huawei.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).