From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH 1/3] doc: remove INIT_DEBUG from ena
Date: Fri, 12 Oct 2018 16:42:50 -0700 [thread overview]
Message-ID: <20181012234252.29049-2-stephen@networkplumber.org> (raw)
In-Reply-To: <20181012234252.29049-1-stephen@networkplumber.org>
The ena driver has used dynamic log type to enable init debugging since 18.05
but the documentation still has leftover mention of the config option.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
doc/guides/nics/ena.rst | 4 ----
1 file changed, 4 deletions(-)
diff --git a/doc/guides/nics/ena.rst b/doc/guides/nics/ena.rst
index 695960d4c9f8..34c48575bf71 100644
--- a/doc/guides/nics/ena.rst
+++ b/doc/guides/nics/ena.rst
@@ -113,10 +113,6 @@ Configuration information
* **CONFIG_RTE_LIBRTE_ENA_PMD** (default y): Enables or disables inclusion
of the ENA PMD driver in the DPDK compilation.
-
- * **CONFIG_RTE_LIBRTE_ENA_DEBUG_INIT** (default y): Enables or disables debug
- logging of device initialization within the ENA PMD driver.
-
* **CONFIG_RTE_LIBRTE_ENA_DEBUG_RX** (default n): Enables or disables debug
logging of RX logic within the ENA PMD driver.
--
2.19.1
next prev parent reply other threads:[~2018-10-12 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 23:42 [dpdk-dev] [PATCH 0/3] leftover INIT_DEBUG stuff Stephen Hemminger
2018-10-12 23:42 ` Stephen Hemminger [this message]
2018-10-12 23:42 ` [dpdk-dev] [PATCH 2/3] doc: liquidio remove documentation for old config options Stephen Hemminger
2018-10-12 23:42 ` [dpdk-dev] [PATCH 3/3] qede: remove #ifdef for INIT_DEBUG Stephen Hemminger
2018-10-15 10:10 ` [dpdk-dev] [PATCH 0/3] leftover INIT_DEBUG stuff Ferruh Yigit
2018-10-15 10:13 ` Ferruh Yigit
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=20181012234252.29049-2-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
/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).