netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@nvidia.com>
To: Vikas Gupta <vikas.gupta@broadcom.com>
Cc: dsahern@kernel.org, stephen@networkplumber.org, kuba@kernel.org,
	netdev@vger.kernel.org, edumazet@google.com,
	michael.chan@broadcom.com, andrew.gospodarek@broadcom.com
Subject: Re: [PATCH iproute2-next v6 1/1] devlink: add support for running selftests
Date: Thu, 4 Aug 2022 11:59:15 +0200	[thread overview]
Message-ID: <YuuYc/pSJR9h+Mq1@nanopsycho> (raw)
In-Reply-To: <20220804091802.36136-2-vikas.gupta@broadcom.com>

Thu, Aug 04, 2022 at 11:18:02AM CEST, vikas.gupta@broadcom.com wrote:
>Add commands and helper APIs to run selftests.
>Include a selftest id for a non volatile memory i.e. flash.
>Also, update the man page and bash-completion for selftests
>commands.
>
>Examples:
>$ devlink dev selftests run pci/0000:03:00.0 id flash
>pci/0000:03:00.0:
>    flash:
>      status passed
>
>$ devlink dev selftests show pci/0000:03:00.0
>pci/0000:03:00.0
>      flash
>
>$ devlink dev selftests show pci/0000:03:00.0 -j
>{"selftests":{"pci/0000:03:00.0":["flash"]}}
>
>$ devlink dev selftests run pci/0000:03:00.0 id flash -j
>{"selftests":{"pci/0000:03:00.0":{"flash":{"status":"passed"}}}}
>
>Signed-off-by: Vikas Gupta <vikas.gupta@broadcom.com>

Reviewed-by: Jiri Pirko <jiri@nvidia.com>

Next time, don't send cover letter for a single patch.

  reply	other threads:[~2022-08-04  9:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04  9:18 [PATCH iproute2-next v6 0/1] devlink: add support to run selftest Vikas Gupta
2022-08-04  9:18 ` [PATCH iproute2-next v6 1/1] devlink: add support for running selftests Vikas Gupta
2022-08-04  9:59   ` Jiri Pirko [this message]
2022-08-04 18:40 ` [PATCH iproute2-next v6 0/1] devlink: add support to run selftest 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=YuuYc/pSJR9h+Mq1@nanopsycho \
    --to=jiri@nvidia.com \
    --cc=andrew.gospodarek@broadcom.com \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=vikas.gupta@broadcom.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).