From: Simon Horman <simon.horman@corigine.com>
To: patchwork-bot+netdevbpf@kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us,
netdev@vger.kernel.org, oss-drivers@corigine.com,
roid@nvidia.com, baowen.zheng@corigine.com
Subject: Re: [PATCH net] flow_offload: return EOPNOTSUPP for the unsupported mpls action type
Date: Tue, 14 Dec 2021 15:34:29 +0100 [thread overview]
Message-ID: <20211214143428.GA463@corigine.com> (raw)
In-Reply-To: <163948561032.12013.18199280015544778926.git-patchwork-notify@kernel.org>
On Tue, Dec 14, 2021 at 12:40:10PM +0000, patchwork-bot+netdevbpf@kernel.org wrote:
> Hello:
>
> This patch was applied to netdev/net.git (master)
> by David S. Miller <davem@davemloft.net>:
>
> On Mon, 13 Dec 2021 15:46:04 +0100 you wrote:
> > From: Baowen Zheng <baowen.zheng@corigine.com>
> >
> > We need to return EOPNOTSUPP for the unsupported mpls action type when
> > setup the flow action.
> >
> > In the original implement, we will return 0 for the unsupported mpls
> > action type, actually we do not setup it and the following actions
> > to the flow action entry.
> >
> > [...]
>
> Here is the summary with links:
> - [net] flow_offload: return EOPNOTSUPP for the unsupported mpls action type
> https://git.kernel.org/netdev/net/c/166b6a46b78b
Thanks!
Could I ask for a merge of net into net-next?
The patch above will be a dependency for v7 of our metering offload
patchset.
Ref:
- [PATCH v6 net-next 00/12] allow user to offload tc action to net device
https://lore.kernel.org/netdev/20211209092806.12336-1-simon.horman@corigine.com/
next prev parent reply other threads:[~2021-12-14 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 14:46 [PATCH net] flow_offload: return EOPNOTSUPP for the unsupported mpls action type Simon Horman
2021-12-14 12:40 ` patchwork-bot+netdevbpf
2021-12-14 14:34 ` Simon Horman [this message]
2021-12-14 16:33 ` Jakub Kicinski
2021-12-15 8:03 ` Simon Horman
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=20211214143428.GA463@corigine.com \
--to=simon.horman@corigine.com \
--cc=baowen.zheng@corigine.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=roid@nvidia.com \
--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 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.