DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] [PATCH] add testing requirement for new PMDs
@ 2021-06-24 14:45 Ferruh Yigit
  2021-06-24 15:30 ` Dmitry Kozlyuk
  2021-06-29  8:34 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
  0 siblings, 2 replies; 7+ messages in thread
From: Ferruh Yigit @ 2021-06-24 14:45 UTC (permalink / raw)
  To: web; +Cc: Thomas Monjalon, John McNamara, dev

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,
+that is why it is expected vendors send a release validation report at least in
+the first release that the PMD is upstreamed.
+
 
 ## Tools
 ---
-- 
2.31.1


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [dpdk-dev] [PATCH] add testing requirement for new PMDs
  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
  2021-06-29  8:34 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
  1 sibling, 1 reply; 7+ messages in thread
From: Dmitry Kozlyuk @ 2021-06-24 15:30 UTC (permalink / raw)
  To: Ferruh Yigit; +Cc: web, Thomas Monjalon, John McNamara, dev

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.

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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [dpdk-dev] [PATCH] add testing requirement for new PMDs
  2021-06-24 15:30 ` Dmitry Kozlyuk
@ 2021-06-29  8:01   ` Ferruh Yigit
  0 siblings, 0 replies; 7+ messages in thread
From: Ferruh Yigit @ 2021-06-29  8:01 UTC (permalink / raw)
  To: Dmitry Kozlyuk; +Cc: web, Thomas Monjalon, John McNamara, dev

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
>>  ---
> 


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [dpdk-dev] [PATCH v2] add testing requirement for new PMDs
  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:34 ` Ferruh Yigit
  2021-07-01  6:49   ` Mcnamara, John
  1 sibling, 1 reply; 7+ messages in thread
From: Ferruh Yigit @ 2021-06-29  8:34 UTC (permalink / raw)
  To: web; +Cc: dev, Thomas Monjalon, John McNamara, Dmitry Kozlyuk

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
Cc: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>

v2:
* 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
 ---
-- 
2.31.1


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [dpdk-dev] [PATCH v2] add testing requirement for new PMDs
  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
  0 siblings, 1 reply; 7+ messages in thread
From: Mcnamara, John @ 2021-07-01  6:49 UTC (permalink / raw)
  To: Yigit, Ferruh, web; +Cc: dev, Thomas Monjalon, Dmitry Kozlyuk

> -----Original Message-----
> From: Yigit, Ferruh <ferruh.yigit@intel.com>
> Sent: Tuesday, June 29, 2021 9:35 AM
> To: web@dpdk.org
> Cc: dev@dpdk.org; Thomas Monjalon <thomas@monjalon.net>; Mcnamara, John
> <john.mcnamara@intel.com>; Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
> Subject: [PATCH v2] add testing requirement for new PMDs
> 
> 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.

Acked-by: John McNamara <john.mcnamara@intel.com>

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [dpdk-dev] [PATCH v2] add testing requirement for new PMDs
  2021-07-01  6:49   ` Mcnamara, John
@ 2021-07-04 15:47     ` Andrew Rybchenko
  2021-07-14 15:10       ` Thomas Monjalon
  0 siblings, 1 reply; 7+ messages in thread
From: Andrew Rybchenko @ 2021-07-04 15:47 UTC (permalink / raw)
  To: Mcnamara, John, Yigit, Ferruh, web; +Cc: dev, Thomas Monjalon, Dmitry Kozlyuk

On 7/1/21 9:49 AM, Mcnamara, John wrote:
>> -----Original Message-----
>> From: Yigit, Ferruh <ferruh.yigit@intel.com>
>> Sent: Tuesday, June 29, 2021 9:35 AM
>> To: web@dpdk.org
>> Cc: dev@dpdk.org; Thomas Monjalon <thomas@monjalon.net>; Mcnamara, John
>> <john.mcnamara@intel.com>; Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
>> Subject: [PATCH v2] add testing requirement for new PMDs
>>
>> 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.
> 
> Acked-by: John McNamara <john.mcnamara@intel.com>
> 

Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [dpdk-dev] [PATCH v2] add testing requirement for new PMDs
  2021-07-04 15:47     ` Andrew Rybchenko
@ 2021-07-14 15:10       ` Thomas Monjalon
  0 siblings, 0 replies; 7+ messages in thread
From: Thomas Monjalon @ 2021-07-14 15:10 UTC (permalink / raw)
  To: Yigit, Ferruh, Andrew Rybchenko; +Cc: Mcnamara, John, web, dev, Dmitry Kozlyuk

04/07/2021 17:47, Andrew Rybchenko:
> On 7/1/21 9:49 AM, Mcnamara, John wrote:
> > From: Yigit, Ferruh <ferruh.yigit@intel.com>
> >> 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.
> > 
> > Acked-by: John McNamara <john.mcnamara@intel.com>
> 
> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>

Acked-by: Thomas Monjalon <thomas@monjalon.net>

Applied, thanks



^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2021-07-14 15:10 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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

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