All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Oz Shlomo <ozsh@nvidia.com>
Cc: netdev@vger.kernel.org, baowen.zheng@corigine.com,
	simon.horman@corigine.com, davem@davemloft.net, roid@nvidia.com
Subject: Re: [PATCH net v2] net/sched: cls_api: Fix flow action initialization
Date: Wed, 20 Jul 2022 10:00:13 +0000	[thread overview]
Message-ID: <165831121305.3977.9754621771164820109.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220719122409.18703-1-ozsh@nvidia.com>

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Tue, 19 Jul 2022 15:24:09 +0300 you wrote:
> The cited commit refactored the flow action initialization sequence to
> use an interface method when translating tc action instances to flow
> offload objects. The refactored version skips the initialization of the
> generic flow action attributes for tc actions, such as pedit, that allocate
> more than one offload entry. This can cause potential issues for drivers
> mapping flow action ids.
> 
> [...]

Here is the summary with links:
  - [net,v2] net/sched: cls_api: Fix flow action initialization
    https://git.kernel.org/netdev/net/c/c0f47c2822aa

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-07-20 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 12:24 [PATCH net v2] net/sched: cls_api: Fix flow action initialization Oz Shlomo
2022-07-20  9:19 ` Baowen Zheng
2022-07-20 10:00 ` 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=165831121305.3977.9754621771164820109.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=baowen.zheng@corigine.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=ozsh@nvidia.com \
    --cc=roid@nvidia.com \
    --cc=simon.horman@corigine.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.