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 v5 2/2] devlink: add support for running selftests
Date: Wed, 3 Aug 2022 12:12:45 +0200 [thread overview]
Message-ID: <YupKHSDx+7Q4K4Qj@nanopsycho> (raw)
In-Reply-To: <20220803091025.30800-3-vikas.gupta@broadcom.com>
Wed, Aug 03, 2022 at 11:10:25AM 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>
prev parent reply other threads:[~2022-08-03 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 9:10 [PATCH iproute2-next v5 0/2] devlink: add support to run selftest Vikas Gupta
2022-08-03 9:10 ` [PATCH iproute2-next v5 1/2] devlink: update the devlink.h Vikas Gupta
2022-08-03 15:10 ` David Ahern
2022-08-03 9:10 ` [PATCH iproute2-next v5 2/2] devlink: add support for running selftests Vikas Gupta
2022-08-03 10:12 ` Jiri Pirko [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=YupKHSDx+7Q4K4Qj@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