DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: thomas@monjalon.net, dev@dpdk.org
Subject: Re: [v2 1/2] doc: add policy for adding vendor PMD specific examples
Date: Thu, 3 Oct 2024 19:59:30 -0700	[thread overview]
Message-ID: <20241003195930.715b83dd@hermes.local> (raw)
In-Reply-To: <20230705095626.31177-1-hemant.agrawal@nxp.com>

On Wed,  5 Jul 2023 15:26:25 +0530
Hemant Agrawal <hemant.agrawal@nxp.com> wrote:

> This patch update the dpdk sample app policy to support
> vendor PMD specific test examples in the respective drivers
> sub-directory in examples.
> 
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> Acked-by: Jerin Jacob <jerinj@marvell.com>

Acked-by: Stephen Hemminger <stephen@networkplumber.org>

      parent reply	other threads:[~2024-10-04  3:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26  7:47 [dpdk-dev] [PATCH " Hemant Agrawal
2021-05-26  7:47 ` [dpdk-dev] [PATCH 2/2] examples: move vendor specific apps to drivers sub directory Hemant Agrawal
2021-06-17  7:17   ` Thomas Monjalon
2021-07-05  8:53     ` Jerin Jacob
2021-11-17 11:02       ` Thomas Monjalon
2021-07-05  8:49   ` Jerin Jacob
2021-11-17 11:01   ` Thomas Monjalon
2021-07-05  8:47 ` [dpdk-dev] [PATCH 1/2] doc: add policy for adding vendor PMD specific examples Jerin Jacob
2021-11-17 10:57 ` Thomas Monjalon
2023-07-03 23:30   ` Stephen Hemminger
2023-07-05  9:56 ` [v2 " Hemant Agrawal
2023-07-05  9:56   ` [v2 2/2] examples: move vendor specific apps to drivers sub directory Hemant Agrawal
2024-10-04  2:59     ` Stephen Hemminger
2023-07-06  5:00   ` [v2 1/2] doc: add policy for adding vendor PMD specific examples Jerin Jacob
2023-10-31 20:02     ` Stephen Hemminger
2024-10-04  2:59   ` Stephen Hemminger [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=20241003195930.715b83dd@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=thomas@monjalon.net \
    /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).