All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: web@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
	John McNamara <john.mcnamara@intel.com>,
	dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] add testing requirement for new PMDs
Date: Tue, 29 Jun 2021 09:01:35 +0100	[thread overview]
Message-ID: <4c31fa8a-98e2-c6d0-b669-2f6f5d262f5a@intel.com> (raw)
In-Reply-To: <20210624183004.60afaf74@sovereign>

On 6/24/2021 4:30 PM, Dmitry Kozlyuk wrote:
> 2021-06-24 15:45 (UTC+0100), Ferruh Yigit:
>> As discussed in the technical board meeting
>> https://mails.dpdk.org/archives/dev/2021-February/200012.html
>>
>> 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
>> ---
>>  content/testing/_index.md | 4 ++++
>>  1 file changed, 4 insertions(+)
>>
>> diff --git a/content/testing/_index.md b/content/testing/_index.md
>> index fcdc47feca9a..3e430f8640af 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.
>>  
>> +It is not easy (or not possible at all) to test PMDs other than device vendors,
> 
> I'm not a native speaker, but is "for" missing (to do X is easy for Y)?
> Suggestion: for anyone other than device vendors.
> 

Thanks Dmitry, I consulted to John for it, I am sending a new version soon.

>> +that is why it is expected vendors send a release validation report at least in
>> +the first release that the PMD is upstreamed.
>> +
>>  
>>  ## Tools
>>  ---
> 


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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24 14:45 [dpdk-dev] [PATCH] add testing requirement for new PMDs Ferruh Yigit
2021-06-24 15:30 ` Dmitry Kozlyuk
2021-06-29  8:01   ` Ferruh Yigit [this message]
2021-06-29  8:34 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2021-07-01  6:49   ` Mcnamara, John
2021-07-04 15:47     ` 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:
  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=4c31fa8a-98e2-c6d0-b669-2f6f5d262f5a@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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.