netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Parav Pandit <parav@nvidia.com>,
	netdev@vger.kernel.org, stephen@networkplumber.org,
	dsahern@kernel.org
Cc: Jiri Pirko <jiri@nvidia.com>
Subject: Re: [PATCH iproute2-next] devlink: Extend man page for port function set command
Date: Wed, 2 Dec 2020 20:41:56 -0700	[thread overview]
Message-ID: <dcabfc2d-d376-ca0f-55e9-983380636298@gmail.com> (raw)
In-Reply-To: <20201130164712.571540-1-parav@nvidia.com>

On 11/30/20 9:47 AM, Parav Pandit wrote:
> Extended devlink-port man page for synopsis, description and
> example for setting devlink port function attribute.
> 
> Signed-off-by: Parav Pandit <parav@nvidia.com>
> Reviewed-by: Jiri Pirko <jiri@nvidia.com>
> ---
>  man/man8/devlink-port.8 | 21 +++++++++++++++++++++
>  1 file changed, 21 insertions(+)
> 
> diff --git a/man/man8/devlink-port.8 b/man/man8/devlink-port.8
> index 966faae6..7e2dc110 100644
> --- a/man/man8/devlink-port.8
> +++ b/man/man8/devlink-port.8
> @@ -46,6 +46,12 @@ devlink-port \- devlink port configuration
>  .ti -8
>  .B devlink port help
>  
> +.ti -8
> +.BR "devlink port function set "

The command exists in iproute2 main branch correct?


  reply	other threads:[~2020-12-03  3:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 16:47 [PATCH iproute2-next] devlink: Extend man page for port function set command Parav Pandit
2020-12-03  3:41 ` David Ahern [this message]
2020-12-03  6:33   ` Parav Pandit
2021-01-22  5:02 ` [PATCH iproute2-next RESEND] " Parav Pandit
2021-01-26 13:23   ` Parav Pandit
2021-01-29  6:35     ` Parav Pandit

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=dcabfc2d-d376-ca0f-55e9-983380636298@gmail.com \
    --to=dsahern@gmail.com \
    --cc=dsahern@kernel.org \
    --cc=jiri@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=parav@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).