mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>
To: netdev@vger.kernel.org
Cc: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Donald Hunter" <donald.hunter@gmail.com>,
	"Danielle Ratson" <danieller@nvidia.com>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Simon Horman" <horms@kernel.org>,
	linux-kernel@vger.kernel.org,
	"Jamal Hadi Salim" <jhs@mojatatu.com>,
	"Jonas Köppeler" <j.koeppeler@tu-berlin.de>,
	"Toke Høiland-Jørgensen" <toke@redhat.com>
Subject: [PATCH net-next v2 8/9] netlink: specs: tc: fix typo in cls-flags
Date: Fri, 25 Sep 2026 21:39:11 +0000	[thread overview]
Message-ID: <20260925213918.204767-9-ast@fiberby.net> (raw)
In-Reply-To: <20260925213918.204767-1-ast@fiberby.net>

Fix a typo in the naming of a cls-flags constant.

The correct name for TCA_CLS_FLAGS_NOT_IN_HW is "not-in-hw",
not "not-in-nw".

CC: Jamal Hadi Salim <jhs@mojatatu.com>
CC: "Jonas Köppeler" <j.koeppeler@tu-berlin.de>
Reviewed-by: Toke Høiland-Jørgensen <toke@redhat.com>
Reviewed-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Asbjørn Sloth Tønnesen <ast@fiberby.net>
---
Note for Sashiko/Clashiko: Targeting net-next, so no "Fixes" tag.

 Documentation/netlink/specs/tc.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/netlink/specs/tc.yaml b/Documentation/netlink/specs/tc.yaml
index 2e663333a279..b6ccc645b0e3 100644
--- a/Documentation/netlink/specs/tc.yaml
+++ b/Documentation/netlink/specs/tc.yaml
@@ -42,7 +42,7 @@ definitions:
       - skip-hw
       - skip-sw
       - in-hw
-      - not-in-nw
+      - not-in-hw
       - verbose
   -
     name: flower-key-ctrl-flags
-- 
2.55.0


  parent reply	other threads:[~2026-09-25 21:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 21:39 [PATCH net-next v2 0/9] netlink: specs: enum alignment fixes Asbjørn Sloth Tønnesen
2026-09-25 21:39 ` [PATCH net-next v2 1/9] netlink: specs: rt-link: re-align IPv4 devconf Asbjørn Sloth Tønnesen
2026-09-25 21:39 ` [PATCH net-next v2 2/9] netlink: specs: rt-link: re-align ifla-inet6-stats Asbjørn Sloth Tønnesen
2026-09-25 21:39 ` [PATCH net-next v2 3/9] netlink: specs: rt-link: fix ifinfo-flags names Asbjørn Sloth Tønnesen
2026-09-25 21:39 ` [PATCH net-next v2 4/9] netlink: specs: devlink: fix resource-scope type Asbjørn Sloth Tønnesen
2026-09-25 21:39 ` [PATCH net-next v2 5/9] netlink: specs: ethtool: re-align c33-pse-ext-state Asbjørn Sloth Tønnesen
2026-09-25 21:39 ` [PATCH net-next v2 6/9] netlink: specs: ethtool: re-align module-fw-flash-status Asbjørn Sloth Tønnesen
2026-09-25 21:39 ` [PATCH net-next v2 7/9] netlink: specs: nl80211: fix naming of enum members Asbjørn Sloth Tønnesen
2026-09-25 21:39 ` Asbjørn Sloth Tønnesen [this message]
2026-09-25 21:39 ` [PATCH net-next v2 9/9] netlink: specs: fix incorrect name-prefixes Asbjørn Sloth Tønnesen

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=20260925213918.204767-9-ast@fiberby.net \
    --to=ast@fiberby.net \
    --cc=danieller@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=j.koeppeler@tu-berlin.de \
    --cc=jhs@mojatatu.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=toke@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®