From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Wenzhuo Lu <wenzhuo.lu@intel.com>
Cc: dev@dpdk.org, adrien.mazarguil@6wind.com, konstantin.ananyev@intel.com
Subject: Re: [dpdk-dev] [PATCH] lib/ip_frag: fix IP reassembly not working issue
Date: Mon, 07 Nov 2016 21:27:43 +0100 [thread overview]
Message-ID: <67229791.hG439HiJFh@xps13> (raw)
In-Reply-To: <1478452574-127074-1-git-send-email-wenzhuo.lu@intel.com>
2016-11-06 12:16, Wenzhuo Lu:
> After changing pkt[0] to pkt[], the example IP reassembly is not
> working.
> It's weird because this change is fine. There should be no
> difference between them.
> As a workaround, revert this change.
>
> Fixes: 347a1e037fd3 (lib: use C99 syntax for zero-size arrays)
>
> Reported-by: Huilong Xu <huilongx.xu@intel.com>
> Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
Applied, thanks
Please keep us informed if you understand the issue.
next prev parent reply other threads:[~2016-11-07 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 17:16 Wenzhuo Lu
2016-11-07 20:27 ` Thomas Monjalon [this message]
2016-11-08 0:55 ` Lu, Wenzhuo
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=67229791.hG439HiJFh@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=wenzhuo.lu@intel.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).