From: Hangbin Liu <liuhangbin@gmail.com>
To: netdev@vger.kernel.org
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
David Ahern <dsahern@kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>,
Davide Caratti <dcaratti@redhat.com>,
Pedro Tammela <pctammela@mojatatu.com>,
Marcelo Leitner <mleitner@redhat.com>,
Phil Sutter <psutter@redhat.com>,
Hangbin Liu <liuhangbin@gmail.com>
Subject: [PATCHv2 iproute2 0/2] tc: fix parsing of TCA_EXT_WARN_MSG
Date: Thu, 16 Mar 2023 11:52:40 +0800 [thread overview]
Message-ID: <20230316035242.2321915-1-liuhangbin@gmail.com> (raw)
The TCA_EXT_WARN_MSG enum belongs to __TCA_MAX namespace. We can't use it
in tc action as it use TCA_ROOT_MAX enum. Fix it by adding a new
TCA_ROOT_EXT_WARN_MSG enum.
Hangbin Liu (2):
Revert "tc: m_action: fix parsing of TCA_EXT_WARN_MSG"
tc: m_action: fix parsing of TCA_EXT_WARN_MSG by using different enum
include/uapi/linux/rtnetlink.h | 1 +
tc/m_action.c | 8 +++++++-
2 files changed, 8 insertions(+), 1 deletion(-)
--
2.38.1
next reply other threads:[~2023-03-16 3:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 3:52 Hangbin Liu [this message]
2023-03-16 3:52 ` [PATCHv2 iproute2 1/2] Revert "tc: m_action: fix parsing of TCA_EXT_WARN_MSG" Hangbin Liu
2023-03-16 3:52 ` [PATCHv2 iproute2 2/2] tc: m_action: fix parsing of TCA_EXT_WARN_MSG by using different enum Hangbin Liu
2023-03-19 2:26 ` Stephen Hemminger
2023-03-20 9:18 ` Hangbin Liu
2023-03-16 15:18 ` [PATCHv2 iproute2 0/2] tc: fix parsing of TCA_EXT_WARN_MSG Andrea Claudi
2023-03-19 2:30 ` patchwork-bot+netdevbpf
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=20230316035242.2321915-1-liuhangbin@gmail.com \
--to=liuhangbin@gmail.com \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=mleitner@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=psutter@redhat.com \
--cc=stephen@networkplumber.org \
--cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).