From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Aman Singh <aman.deep.singh@intel.com>,
andrew.rybchenko@oktetlabs.ru
Subject: Re: [PATCH v2] maintainers: update for testpmd
Date: Thu, 25 Nov 2021 17:56:38 +0100 [thread overview]
Message-ID: <2722699.hZtOylHxXI@thomas> (raw)
In-Reply-To: <4f32db0b-8fac-25d6-9555-bac528c39c86@intel.com>
25/11/2021 17:31, Ferruh Yigit:
> On 11/25/2021 4:04 PM, Ferruh Yigit wrote:
> > On 11/25/2021 3:20 PM, Thomas Monjalon wrote:
> >> 25/11/2021 14:40, Ferruh Yigit:
> >>> On 11/25/2021 10:01 AM, Thomas Monjalon wrote:
> >>>> -Driver testing tool
> >>>> +Networking features testing tool
> >>>
> >>> "Networking features" scope is a little wide.
> >>> Not sure if "Networking features" or "Networking drivers" suits better,
> >>> according previous title it is for driver testing.
> >>
> >> Yes it is for drivers features.
> >> I want to distinguish testpmd and other tools like test-flow-perf
> >> which is also testing networking drivers.
> >>
> >> Maybe "Networking drivers features testing tool" ?
> >>
> >
> > ack
> >
>
> thinking twice what additional meaning does 'features' adds here,
> "Networking drivers features testing"
> vs
> "Networking drivers testing"
>
> Isn't "Networking drivers testing" implies features of drivers?
Yes
I was trying to avoid being too generic,
because the same title could apply to flow-perf.
But not mentioning "performance" should be enough.
OK for "Networking drivers testing tool"
next prev parent reply other threads:[~2021-11-25 16:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 7:19 [dpdk-dev] [PATCH] maintainers: update for driver testing tool Aman Singh
2021-10-22 8:57 ` Ferruh Yigit
2021-11-25 10:00 ` Thomas Monjalon
2021-11-25 10:01 ` [PATCH v2] maintainers: update for testpmd Thomas Monjalon
2021-11-25 13:40 ` Ferruh Yigit
2021-11-25 15:20 ` Thomas Monjalon
2021-11-25 16:04 ` Ferruh Yigit
2021-11-25 16:31 ` Ferruh Yigit
2021-11-25 16:56 ` Thomas Monjalon [this message]
2021-11-26 10:04 ` [PATCH v3] " Thomas Monjalon
2021-11-26 11:14 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2022-02-09 15:01 [PATCH v1] " Yuying Zhang
2022-02-10 17:11 ` [PATCH v2] " Yuying Zhang
2022-02-10 10:09 ` Ferruh Yigit
2022-02-09 17:28 [PATCH v1] " Yuying Zhang
2022-02-10 15:03 ` [PATCH v2] " Yuying Zhang
2022-03-08 22:48 ` 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=2722699.hZtOylHxXI@thomas \
--to=thomas@monjalon.net \
--cc=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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 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.