From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Dan Gora <dg@adax.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 18:21:50 +0000 [thread overview]
Message-ID: <5c66a386-ded9-4075-1a72-73d598e7910e@intel.com> (raw)
In-Reply-To: <CAGyogRY-N1s4vf_dfQ48qQHyH5HY_WG_dSXpMDzcaiqQTTY1gg@mail.gmail.com>
On 11/5/2018 6:12 PM, Dan Gora wrote:
> Hi Ferruh,
>
> On Mon, Nov 5, 2018 at 3:28 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>>
>> Commit 89397a01ce4a ("kni: set default carrier state of interface")
>> changes the KNI interface default carrier status. Which prevents traffic
>> flow by default and may break some existing usage / testing.
>>
>> Document this behavior change in release notes.
>>
>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Sorry about this.. I guess I should have done this with the patch series...
>
> The changes here don't include the new module parameter to the KNI
> kernel module. I'll send a new release note patch in a few minutes
> which hopefully covers everything. I guess the test plan
> documentation needs to be updated as well, but I don't know where
> those documents live. Are they separate from the main DPDK source?
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/
next prev parent reply other threads:[~2018-11-05 18:21 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 [this message]
2018-11-05 18:23 ` Dan Gora
2018-11-05 18:34 ` Dan Gora
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=5c66a386-ded9-4075-1a72-73d598e7910e@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=dg@adax.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).