DPDK website maintenance
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: web@dpdk.org
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
	John McNamara <john.mcnamara@intel.com>,
	Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Subject: [dpdk-web] [PATCH v2] add testing requirement for new PMDs
Date: Tue, 29 Jun 2021 09:34:32 +0100	[thread overview]
Message-ID: <20210629083432.1803007-1-ferruh.yigit@intel.com> (raw)
In-Reply-To: <20210624144513.3094257-1-ferruh.yigit@intel.com>

As discussed in the technical board meeting

This is to record that new upstreamed devices tested adequately.

Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
CC: John McNamara <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Cc: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>

* Paragraph reworded.
 content/testing/_index.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/content/testing/_index.md b/content/testing/_index.md
index fcdc47feca9a..7504df0f7cae 100644
--- a/content/testing/_index.md
+++ b/content/testing/_index.md
@@ -116,6 +116,10 @@ some validation reports are requested to the community members.
 Such release validations are sent as replies to the release announcement.
+Some PMDs can be tested only by their owners. That is why it is expected that
+device vendors send a release validation report, at least in the first release
+that the PMD is upstreamed.
 ## Tools

  parent reply	other threads:[~2021-06-29  8:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24 14:45 [dpdk-web] [PATCH] " Ferruh Yigit
2021-06-24 15:30 ` [dpdk-web] [dpdk-dev] " Dmitry Kozlyuk
2021-06-29  8:01   ` Ferruh Yigit
2021-06-29  8:34 ` Ferruh Yigit [this message]
2021-07-01  6:49   ` [dpdk-web] [PATCH v2] " Mcnamara, John
2021-07-04 15:47     ` [dpdk-web] [dpdk-dev] " Andrew Rybchenko
2021-07-14 15:10       ` Thomas Monjalon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210629083432.1803007-1-ferruh.yigit@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=john.mcnamara@intel.com \
    --cc=thomas@monjalon.net \
    --cc=web@dpdk.org \


* 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).