From: "Singh, Aman Deep" <aman.deep.singh@intel.com>
To: "viacheslavo@nvidia.com" <viacheslavo@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"orika@nvidia.com" <orika@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [RFC 3/3] app/testpmd: fix hex string parser in flow commands
Date: Wed, 29 Sep 2021 12:22:43 +0000 [thread overview]
Message-ID: <CY4PR11MB1367BA7923A136D5109AD7C4A3A99@CY4PR11MB1367.namprd11.prod.outlook.com> (raw)
Hi Ovsiienko,
Can you please provide the flow command which causes "segmentation fault".
Thanks
Aman
next reply other threads:[~2021-09-29 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 12:22 Singh, Aman Deep [this message]
2021-09-29 13:30 ` Slava Ovsiienko
-- strict thread matches above, loose matches on Subject: below --
2021-09-10 14:16 [dpdk-dev] [RFC 1/3] ethdev: update modify field flow action Viacheslav Ovsiienko
2021-09-10 14:16 ` [dpdk-dev] [RFC 3/3] app/testpmd: fix hex string parser in flow commands Viacheslav Ovsiienko
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=CY4PR11MB1367BA7923A136D5109AD7C4A3A99@CY4PR11MB1367.namprd11.prod.outlook.com \
--to=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@nvidia.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).