All of lore.kernel.org
 help / color / mirror / Atom feed
From: <shaibran@amazon.com>
To: <ferruh.yigit@amd.com>
Cc: <dev@dpdk.org>, Shai Brandes <shaibran@amazon.com>
Subject: [PATCH 3/3] net/ena: remove outdated devarg documentation
Date: Wed, 23 Oct 2024 12:41:19 +0300	[thread overview]
Message-ID: <20241023094119.4299-4-shaibran@amazon.com> (raw)
In-Reply-To: <20241023094119.4299-1-shaibran@amazon.com>

From: Shai Brandes <shaibran@amazon.com>

Removed obsolete devarg enforcing normal llq policy,
as its logic is now handled by the new `llq_policy` devarg.

Signed-off-by: Shai Brandes <shaibran@amazon.com>
---
 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 a40f09be09..a34575dc9b 100644
--- a/doc/guides/nics/ena.rst
+++ b/doc/guides/nics/ena.rst
@@ -120,10 +120,6 @@ Runtime Configuration
 
      3 - Enforce large LLQ policy.
 
-   * **normal_llq_hdr** (default 0)
-
-     Enforce normal LLQ policy.
-
    * **miss_txc_to** (default 5)
 
      Number of seconds after which the Tx packet will be considered missing.
-- 
2.17.1


  parent reply	other threads:[~2024-10-23  9:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23  9:41 [PATCH 0/3] net/ena: ena release 2.11.0 shaibran
2024-10-23  9:41 ` [PATCH 1/3] net/ena: upgrade driver version to 2.11.0 shaibran
2024-10-23  9:41 ` [PATCH 2/3] net/ena: support malformed Rx descriptor error shaibran
2024-10-23  9:41 ` shaibran [this message]
2024-10-30  2:59   ` [PATCH 3/3] net/ena: remove outdated devarg documentation Ferruh Yigit
2024-10-30  2:59 ` [PATCH 0/3] net/ena: ena release 2.11.0 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=20241023094119.4299-4-shaibran@amazon.com \
    --to=shaibran@amazon.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.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.