All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@corigine.com>
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
Subject: Re: [PATCH net-next v5 1/5] net/sched: act_pedit: use NLA_POLICY for parsing 'ex' keys
Date: Sat, 22 Apr 2023 10:17:09 +0200	[thread overview]
Message-ID: <ZEOYBX6GXCdukRy9@corigine.com> (raw)
In-Reply-To: <20230421212516.406726-2-pctammela@mojatatu.com>

On Fri, Apr 21, 2023 at 06:25:13PM -0300, Pedro Tammela wrote:
> Transform two checks in the 'ex' key parsing into netlink policies
> removing extra if checks.
> 
> Signed-off-by: Pedro Tammela <pctammela@mojatatu.com>

Reviewed-by: Simon Horman <simon.horman@corigine.com>


  reply	other threads:[~2023-04-22  8:17 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 [this message]
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 ` [PATCH net-next v5 0/5] net/sched: act_pedit: minor improvements patchwork-bot+netdevbpf

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=ZEOYBX6GXCdukRy9@corigine.com \
    --to=simon.horman@corigine.com \
    --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=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.