DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Harman Kalra <hkalra@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] test/bpf: add new test cases
Date: Thu, 24 Oct 2019 09:56:55 +0200	[thread overview]
Message-ID: <CAJFAV8zOWaaBvMOt1PkcVba6u-XJ5udQK7B7UdV6qHa5LH221A@mail.gmail.com> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB97725801A8C6A2AE@IRSMSX104.ger.corp.intel.com>

On Thu, Oct 17, 2019 at 1:23 PM Ananyev, Konstantin
<konstantin.ananyev@intel.com> wrote:
>
> > This patch implements following new test cases:
> > - test_call4: test case to verify if stack corruption occurs
> > across with multiple function calls.
> > - test_jump2: test case with a default packet in memory, parse
> > the packet and check if dest ip is part of a subnet.
> > - test_call5: test case with string data in the stack and
> > calling string comaprision.
> >
> > Signed-off-by: Harman Kalra <hkalra@marvell.com>
> > ---
> > V2 Changes:
> > * Maintaining uniformity across the code by using cmp_res rather than
> > individual if statements.
> >
> >  app/test/test_bpf.c | 619 ++++++++++++++++++++++++++++++++++++++++++++
> >  1 file changed, 619 insertions(+)
> > --
>
> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>

Applied, thanks.


-- 
David Marchand


      reply	other threads:[~2019-10-24  7:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24 15:20 [dpdk-dev] [PATCH] " Harman Kalra
2019-09-24 17:14 ` Ananyev, Konstantin
2019-09-25 10:43   ` [dpdk-dev] [PATCH v2] " Harman Kalra
2019-10-14 14:09     ` Harman Kalra
2019-10-17 11:23     ` Ananyev, Konstantin
2019-10-24  7:56       ` David Marchand [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=CAJFAV8zOWaaBvMOt1PkcVba6u-XJ5udQK7B7UdV6qHa5LH221A@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hkalra@marvell.com \
    --cc=konstantin.ananyev@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).