From: Donald Hunter <donald.hunter@gmail.com>
To: Ido Schimmel <idosch@idosch.org>
Cc: netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
donald.hunter@redhat.com, gnault@redhat.com
Subject: Re: [PATCH net-next v1 2/2] netlink: specs: Add a spec for FIB rule management
Date: Tue, 05 Nov 2024 11:06:06 +0000 [thread overview]
Message-ID: <m234k6vt29.fsf@gmail.com> (raw)
In-Reply-To: <ZykRRvZ-lvfEz_EG@shredder> (Ido Schimmel's message of "Mon, 4 Nov 2024 20:24:06 +0200")
Ido Schimmel <idosch@idosch.org> writes:
>
> Donald,
>
> We added a new DSCP attribute in the last release. Can you please
> include it in the spec? Tested the following diff [1].
>
> Thanks!
>
> [1]
Good catch, thanks! Diff applied for v2.
> diff --git a/Documentation/netlink/specs/rt_rule.yaml b/Documentation/netlink/specs/rt_rule.yaml
> index 736bcdb25738..8d1a594e851d 100644
> --- a/Documentation/netlink/specs/rt_rule.yaml
> +++ b/Documentation/netlink/specs/rt_rule.yaml
> @@ -169,6 +169,9 @@ attribute-sets:
> name: dport-range
> type: binary
> struct: fib-rule-port-range
> + -
> + name: dscp
> + type: u8
>
> operations:
> enum-model: directional
> @@ -199,6 +202,7 @@ operations:
> - ip-proto
> - sport-range
> - dport-range
> + - dscp
> -
> name: newrule-ntf
> doc: Notify a rule creation
next prev parent reply other threads:[~2024-11-05 11:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 16:53 [PATCH net-next v1 0/2] netlink: specs: Add neigh and rule YNL specs Donald Hunter
2024-11-04 16:53 ` [PATCH net-next v1 1/2] netlink: specs: Add a spec for neighbor tables in rtnetlink Donald Hunter
2024-11-04 16:53 ` [PATCH net-next v1 2/2] netlink: specs: Add a spec for FIB rule management Donald Hunter
2024-11-04 18:24 ` Ido Schimmel
2024-11-05 11:06 ` Donald Hunter [this message]
2024-11-04 18:45 ` Stanislav Fomichev
2024-11-05 11:10 ` Donald Hunter
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=m234k6vt29.fsf@gmail.com \
--to=donald.hunter@gmail.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@redhat.com \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=horms@kernel.org \
--cc=idosch@idosch.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).