test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Mykola Kostenok <mko-plv@napatech.com>,
	"Tu, Lijuan" <lijuan.tu@intel.com>
Cc: "dts@dpdk.org" <dts@dpdk.org>, Rasmus Carlson <rc@napatech.com>,
	 Maksym Kovaliov <mak-plv@napatech.com>
Subject: Re: Napatech participation in DPDK. DTS related questions.
Date: Mon, 21 Aug 2023 11:58:17 +0200	[thread overview]
Message-ID: <CAOb5WZbTiNfEvRhjNnwLwtVUkG-in=SRxQk2RE3Z8S--W6nfzw@mail.gmail.com> (raw)
In-Reply-To: <AS1P190MB1797C4FFAF728AC00F8C6BF69F0DA@AS1P190MB1797.EURP190.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 734 bytes --]

Hi Lijuan,

Could you please clarify the timeline query from the Napatech folks? I
believe DTS patches can be accepted at any time, so the only timeline
considerations are on the DPDK side, but please confirm.

Thanks,
Juraj

On Tue, Aug 15, 2023 at 7:21 PM Mykola Kostenok <mko-plv@napatech.com>
wrote:

> Hi,
>
> Please clarify the timeline for the current DTS release. How is this
> timeline correlated with DPDK timeline?
>
> We plan to upstream PMD driver, and we would like to understand the
> amount/set of tests required to be upstreamed in parallel.
>
> Currently we have DTS tests that mostly cover rte_flow functionality of
> Napatech NICs.
>
>
>
> Best regards,
>
> Mykola Kostenok.
>
>
>

[-- Attachment #2: Type: text/html, Size: 1990 bytes --]

      reply	other threads:[~2023-08-21  9:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08 14:54 Mykola Kostenok
2023-08-21  9:58 ` Juraj Linkeš [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='CAOb5WZbTiNfEvRhjNnwLwtVUkG-in=SRxQk2RE3Z8S--W6nfzw@mail.gmail.com' \
    --to=juraj.linkes@pantheon.tech \
    --cc=dts@dpdk.org \
    --cc=lijuan.tu@intel.com \
    --cc=mak-plv@napatech.com \
    --cc=mko-plv@napatech.com \
    --cc=rc@napatech.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 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).