netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@nvidia.com>
To: <netdev@vger.kernel.org>
Cc: <dsahern@gmail.com>, <stephen@networkplumber.org>,
	<gnault@redhat.com>, <petrm@nvidia.com>,
	Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH iproute2-next 0/2] iprule: Add DSCP support
Date: Wed, 9 Oct 2024 09:20:52 +0300	[thread overview]
Message-ID: <20241009062054.526485-1-idosch@nvidia.com> (raw)

Add DSCP selector support to ip-rule following kernel support that was
added in kernel commit 7bb50f30c123 ("Merge branch
'net-fib_rules-add-dscp-selector-support'").

Patch #1 adds ip-rule(8) as generation target so that we could use
variable substitutions there in a similar fashion to other man pages.

Patch #2 adds actual support. See the commit message for example usage
and output.

Ido Schimmel (2):
  man: Add ip-rule(8) as generation target
  iprule: Add DSCP support

 include/rt_names.h                   |  2 ++
 ip/iprule.c                          | 36 ++++++++++++++++++++++++++++
 lib/rt_names.c                       | 23 ++++++++++++++++++
 man/man8/.gitignore                  |  1 +
 man/man8/Makefile                    |  2 +-
 man/man8/{ip-rule.8 => ip-rule.8.in} | 17 +++++++++++++
 6 files changed, 80 insertions(+), 1 deletion(-)
 rename man/man8/{ip-rule.8 => ip-rule.8.in} (93%)

-- 
2.46.2


             reply	other threads:[~2024-10-09  6:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09  6:20 Ido Schimmel [this message]
2024-10-09  6:20 ` [PATCH iproute2-next 1/2] man: Add ip-rule(8) as generation target Ido Schimmel
2024-10-10 11:59   ` Daniel Machon
2024-10-10 22:14   ` Guillaume Nault
2024-10-09  6:20 ` [PATCH iproute2-next 2/2] iprule: Add DSCP support Ido Schimmel
2024-10-10 12:00   ` Daniel Machon
2024-10-10 22:14   ` Guillaume Nault
2024-10-11  0:30 ` [PATCH iproute2-next 0/2] " 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=20241009062054.526485-1-idosch@nvidia.com \
    --to=idosch@nvidia.com \
    --cc=dsahern@gmail.com \
    --cc=gnault@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=petrm@nvidia.com \
    --cc=stephen@networkplumber.org \
    /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).