netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Pedro Tammela <pctammela@mojatatu.com>
Cc: netdev@vger.kernel.org, jhs@mojatatu.com,
	xiyou.wangcong@gmail.com, jiri@resnulli.us, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	simon.horman@corigine.com
Subject: Re: [PATCH net-next v5 0/5] net/sched: act_pedit: minor improvements
Date: Sun, 23 Apr 2023 17:40:19 +0000	[thread overview]
Message-ID: <168227161902.13607.15005287783913046062.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230421212516.406726-1-pctammela@mojatatu.com>

Hello:

This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Fri, 21 Apr 2023 18:25:12 -0300 you wrote:
> This series aims to improve the code and usability of act_pedit for
> netlink users.
> 
> Patches 1-2 improves error reporting for extended keys parsing with extack.
> 
> Patch 3 checks the static offsets a priori on create/update. Currently,
> this is done at the datapath for both static and runtime offsets.
> 
> [...]

Here is the summary with links:
  - [net-next,v5,1/5] net/sched: act_pedit: use NLA_POLICY for parsing 'ex' keys
    https://git.kernel.org/netdev/net-next/c/5036034572b7
  - [net-next,v5,2/5] net/sched: act_pedit: use extack in 'ex' parsing errors
    https://git.kernel.org/netdev/net-next/c/0c83c5210e18
  - [net-next,v5,3/5] net/sched: act_pedit: check static offsets a priori
    https://git.kernel.org/netdev/net-next/c/e1201bc781c2
  - [net-next,v5,4/5] net/sched: act_pedit: remove extra check for key type
    https://git.kernel.org/netdev/net-next/c/577140180ba2
  - [net-next,v5,5/5] net/sched: act_pedit: rate limit datapath messages
    https://git.kernel.org/netdev/net-next/c/e3c9673e2f6e

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



      parent reply	other threads:[~2023-04-23 17:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21 21:25 [PATCH net-next v5 0/5] net/sched: act_pedit: minor improvements Pedro Tammela
2023-04-21 21:25 ` [PATCH net-next v5 1/5] net/sched: act_pedit: use NLA_POLICY for parsing 'ex' keys Pedro Tammela
2023-04-22  8:17   ` Simon Horman
2023-04-21 21:25 ` [PATCH net-next v5 2/5] net/sched: act_pedit: use extack in 'ex' parsing errors Pedro Tammela
2023-04-21 21:25 ` [PATCH net-next v5 3/5] net/sched: act_pedit: check static offsets a priori Pedro Tammela
2023-04-25 12:13   ` Ido Schimmel
2023-04-25 12:27     ` Pedro Tammela
2023-04-25 13:36       ` Ido Schimmel
2023-04-21 21:25 ` [PATCH net-next v5 4/5] net/sched: act_pedit: remove extra check for key type Pedro Tammela
2023-04-21 21:25 ` [PATCH net-next v5 5/5] net/sched: act_pedit: rate limit datapath messages Pedro Tammela
2023-04-23 17: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=168227161902.13607.15005287783913046062.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pctammela@mojatatu.com \
    --cc=simon.horman@corigine.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 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).