DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dan Gora <dg@adax.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>,
	dev@dpdk.org,  Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] doc: update release notes for default KNI carries status
Date: Mon, 5 Nov 2018 16:34:26 -0200	[thread overview]
Message-ID: <CAGyogRZH7n9YHNNM--fm5vdnmbtPjS9jgSVUaoLFQY-7ct93Jw@mail.gmail.com> (raw)
In-Reply-To: <CAGyogRaWCt8Ox_7mvqFbZSf6+JHL_5K--ZEjMXKZSs1LfPZ6VQ@mail.gmail.com>

On Mon, Nov 5, 2018 at 4:23 PM Dan Gora <dg@adax.com> wrote:
>
> On Mon, Nov 5, 2018 at 4:21 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> > There is no test plan documentation within dpdk repo. There is DTS (dpdk test
> > suit) in a separate repo [1], which needs to be updated, and indeed this patch
> > is to point them the change because existing test is failing after changes...
> >
> > [1]
> > https://git.dpdk.org/tools/dts/
>
> Should patches for the DTS get sent to this list (dev@dpdk.org) as
> well or is there are separate list for those?

Never mind.. It's in the CONTRIBUTING.TXT file.. RTFM, dan..

======
Contributions to DTS should be submitted as git formatted patches to the
DTS mailing list: dts@dpdk.org
======

  reply	other threads:[~2018-11-05 18:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05 17:28 Ferruh Yigit
2018-11-05 18:12 ` Dan Gora
2018-11-05 18:21   ` Ferruh Yigit
2018-11-05 18:23     ` Dan Gora
2018-11-05 18:34       ` Dan Gora [this message]
2018-11-18 23:24 ` 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=CAGyogRZH7n9YHNNM--fm5vdnmbtPjS9jgSVUaoLFQY-7ct93Jw@mail.gmail.com \
    --to=dg@adax.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=thomas@monjalon.net \
    /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).