From: David Ahern <dsahern@kernel.org>
To: Daniel Zahka <daniel.zahka@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Donald Hunter <donald.hunter@gmail.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH iproute2-next 2/2] devlink: support displaying and resetting to default params
Date: Mon, 17 Nov 2025 17:46:38 -0700 [thread overview]
Message-ID: <698e0349-f392-4c73-804e-bcdf4fab825b@kernel.org> (raw)
In-Reply-To: <20251117-param-defaults-v1-2-c99604175d09@gmail.com>
On 11/17/25 5:40 PM, Daniel Zahka wrote:
> Add devlink cli support default param values.
>
> For param-get, any default values provided by the kernel will be
> displayed next to the current value. For param-set,
> DEVLINK_ATTR_PARAM_RESET_DEFAULT can be included in the request to
> request that the parameter be reset to its default value.
>
> Signed-off-by: Daniel Zahka <daniel.zahka@gmail.com>
> ---
> devlink/devlink.c | 83 +++++++++++++++++++++++++++++++++++++++-----
> include/uapi/linux/devlink.h | 3 ++
uapi changes need to be a separate patch that I can drop when applying.
prev parent reply other threads:[~2025-11-18 0:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 0:40 [PATCH iproute2-next 0/2] devlink: support default flag attr for param-get and param-set commands Daniel Zahka
2025-11-18 0:40 ` [PATCH iproute2-next 1/2] devlink: Pull the value printing logic out of pr_out_param_value() Daniel Zahka
2025-11-18 16:02 ` Stephen Hemminger
2025-11-18 0:40 ` [PATCH iproute2-next 2/2] devlink: support displaying and resetting to default params Daniel Zahka
2025-11-18 0:46 ` David Ahern [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=698e0349-f392-4c73-804e-bcdf4fab825b@kernel.org \
--to=dsahern@kernel.org \
--cc=daniel.zahka@gmail.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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).