From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
f.fainelli@gmail.com, andrew@lunn.ch, vivien.didelot@gmail.com,
olteanv@gmail.com, claudiu.manoil@nxp.com,
alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net] net: mscc: ocelot: fix backwards compatibility with single-chain tc-flower offload
Date: Thu, 17 Mar 2022 16:40:11 +0000 [thread overview]
Message-ID: <164753521128.23544.9613748654792250011.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220316192117.2568261-1-vladimir.oltean@nxp.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 16 Mar 2022 21:21:17 +0200 you wrote:
> ACL rules can be offloaded to VCAP IS2 either through chain 0, or, since
> the blamed commit, through a chain index whose number encodes a specific
> PAG (Policy Action Group) and lookup number.
>
> The chain number is translated through ocelot_chain_to_pag() into a PAG,
> and through ocelot_chain_to_lookup() into a lookup number.
>
> [...]
Here is the summary with links:
- [net] net: mscc: ocelot: fix backwards compatibility with single-chain tc-flower offload
https://git.kernel.org/netdev/net/c/8e0341aefcc9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-03-17 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 19:21 [PATCH net] net: mscc: ocelot: fix backwards compatibility with single-chain tc-flower offload Vladimir Oltean
2022-03-17 16:40 ` patchwork-bot+netdevbpf [this message]
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=164753521128.23544.9613748654792250011.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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).