All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Aman Sharma <amanrsdev@gmail.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org, amasharm@redhat.com
Subject: Re: [PATCH iproute2-next] ip-route2: document uid parameter for route get
Date: Wed, 16 Sep 2026 08:43:41 -0700	[thread overview]
Message-ID: <20260916084341.1a393857@phoenix.local> (raw)
In-Reply-To: <20260916105759.742997-1-amanrsdev@gmail.com>

On Wed, 16 Sep 2026 16:27:59 +0530
Aman Sharma <amanrsdev@gmail.com> wrote:

> The 'ip route get' command accepts a 'uid NUMBER' parameter
> to simulate route selection as if sent by a specific user.
> This is useful for testing per-user routing policies.
> 
> Add documentation for this parameter in the 'ip route get'
> section of the man page.
> 
> Signed-off-by: Aman Sharma <amanrsdev@gmail.com>

Applied to iproute2 and added missing SYNOPSIS item as well.

      reply	other threads:[~2026-09-16 15:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 10:57 [PATCH iproute2-next] ip-route2: document uid parameter for route get Aman Sharma
2026-09-16 15:43 ` Stephen Hemminger [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=20260916084341.1a393857@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=amanrsdev@gmail.com \
    --cc=amasharm@redhat.com \
    --cc=dsahern@kernel.org \
    --cc=netdev@vger.kernel.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 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.