From: Jakub Kicinski <kuba@kernel.org>
To: Steen Hegelund <steen.hegelund@microchip.com>
Cc: Casper Andersson <casper.casan@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, <UNGLinuxDriver@microchip.com>,
Randy Dunlap <rdunlap@infradead.org>,
Russell King <rmk+kernel@armlinux.org.uk>,
"Wan Jiabing" <wanjiabing@vivo.com>,
Nathan Huckleberry <nhuck@google.com>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Daniel Machon <daniel.machon@microchip.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
Lars Povlsen <lars.povlsen@microchip.com>
Subject: Re: [PATCH net-next v2 2/5] net: microchip: sparx5: Adding more tc flower keys for the IS2 VCAP
Date: Mon, 31 Oct 2022 18:41:28 -0700 [thread overview]
Message-ID: <20221031184128.1143d51e@kernel.org> (raw)
In-Reply-To: <51622bfd3fe718139cece38493946c2860ebdf77.camel@microchip.com>
On Mon, 31 Oct 2022 13:14:33 +0100 Steen Hegelund wrote:
> > I'm not able to get this working on PCB135. I tested the VLAN tags and
> > did not work either (did not test the rest). The example from the
> > previous patch series doesn't work either after applying this series.
Previous series in this context means previous revision or something
that was already merged?
> tc filter add dev eth3 ingress chain 8000000 prio 10 handle 10 \
How are you using chains?
I thought you need to offload FLOW_ACTION_GOTO to get to a chain,
and I get no hits on this driver.
next prev parent reply other threads:[~2022-11-01 1:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 14:45 [PATCH net-next v2 0/5] Extend TC key support for Sparx5 IS2 VCAP Steen Hegelund
2022-10-28 14:45 ` [PATCH net-next v2 1/5] net: microchip: sparx5: Differentiate IPv4 and IPv6 traffic in keyset config Steen Hegelund
2022-10-28 14:45 ` [PATCH net-next v2 2/5] net: microchip: sparx5: Adding more tc flower keys for the IS2 VCAP Steen Hegelund
2022-10-31 10:44 ` Casper Andersson
2022-10-31 12:14 ` Steen Hegelund
2022-10-31 14:52 ` Casper Andersson
2022-10-31 15:51 ` Steen Hegelund
2022-11-01 1:41 ` Jakub Kicinski [this message]
2022-11-01 7:31 ` Steen Hegelund
2022-11-01 15:49 ` Jakub Kicinski
2022-11-01 19:32 ` Steen Hegelund
2022-11-02 13:11 ` Steen Hegelund
2022-11-03 1:28 ` Jakub Kicinski
2022-11-03 16:21 ` Steen Hegelund
2022-10-28 14:45 ` [PATCH net-next v2 3/5] net: microchip: sparx5: Match keys in configured port keysets Steen Hegelund
2022-10-28 14:45 ` [PATCH net-next v2 4/5] net: microchip: sparx5: Let VCAP API validate added key- and actionfields Steen Hegelund
2022-10-28 14:45 ` [PATCH net-next v2 5/5] net: microchip: sparx5: Adding KUNIT tests of key/action values in VCAP API Steen Hegelund
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=20221031184128.1143d51e@kernel.org \
--to=kuba@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=casper.casan@gmail.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhuck@google.com \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=steen.hegelund@microchip.com \
--cc=wanjiabing@vivo.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).