The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andreas Karis <ak.karis@gmail.com>
To: linux-doc@vger.kernel.org
Cc: ak.karis@gmail.com, linux-kernel@vger.kernel.org,
	davem@davemloft.net, netdev@vger.kernel.org, corbet@lwn.net
Subject: [PATCH] docs: networking: Remove VLAN_TAG_PRESENT from openvswitch doc
Date: Wed, 29 Jan 2025 17:06:25 +0100	[thread overview]
Message-ID: <20250129160625.97979-1-ak.karis@gmail.com> (raw)

Since commit 0c4b2d370514cb4f3454dd3b18f031d2651fab73
("net: remove VLAN_TAG_PRESENT"), the kernel no longer sets the DEI/CFI
bit in __vlan_hwaccel_put_tag to indicate the presence of a VLAN tag.
Update the openvswitch documentation which still contained an outdated
reference to this mechanism.

Signed-off-by: Andreas Karis <ak.karis@gmail.com>
---
 Documentation/networking/openvswitch.rst | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/Documentation/networking/openvswitch.rst b/Documentation/networking/openvswitch.rst
index 1a8353dbf1b6..5699bbadea47 100644
--- a/Documentation/networking/openvswitch.rst
+++ b/Documentation/networking/openvswitch.rst
@@ -230,11 +230,9 @@ an all-zero-bits vlan and an empty encap attribute, like this::
     eth(...), eth_type(0x8100), vlan(0), encap()
 
 Unlike a TCP packet with source and destination ports 0, an
-all-zero-bits VLAN TCI is not that rare, so the CFI bit (aka
-VLAN_TAG_PRESENT inside the kernel) is ordinarily set in a vlan
-attribute expressly to allow this situation to be distinguished.
-Thus, the flow key in this second example unambiguously indicates a
-missing or malformed VLAN TCI.
+all-zero-bits VLAN TCI is not that rare and the flow key in
+this second example cannot indicate a missing or malformed
+VLAN TCI.
 
 Other rules
 -----------
-- 
2.48.1


             reply	other threads:[~2025-01-29 16:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29 16:06 Andreas Karis [this message]
2025-02-02  0:53 ` [PATCH] docs: networking: Remove VLAN_TAG_PRESENT from openvswitch doc Jakub Kicinski
2025-02-02 20:55 ` Ilya Maximets

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=20250129160625.97979-1-ak.karis@gmail.com \
    --to=ak.karis@gmail.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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