public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Vikas Gupta <vikas.gupta@broadcom•com>
To: jiri@nvidia•com, dsahern@kernel•org, stephen@networkplumber•org
Cc: kuba@kernel•org, netdev@vger•kernel.org, edumazet@google•com,
	michael.chan@broadcom•com, andrew.gospodarek@broadcom•com,
	Vikas Gupta <vikas.gupta@broadcom•com>
Subject: [PATCH iproute2-next v2 0/3] devlink: add support to run selftests
Date: Fri,  8 Jul 2022 00:01:13 +0530	[thread overview]
Message-ID: <20220707183116.29422-1-vikas.gupta@broadcom.com> (raw)
In-Reply-To: <20220628164447.45202-1-vikas.gupta@broadcom.com>

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

Hi,
  This patchset adds support in devlink to run selftests.
  A related patchset for kernel has been pushed for review.
  Below are the few examples for the commands.
  
 Examples:
    $ devlink dev selftests run pci/0000:03:00.0 test flash
       selftests results:
          flash failed

    $ devlink dev selftests show pci/0000:03:00.0
       supported selftests:
          flash

changes from:
v1->v2
    a) Changes required to implement command due to changes
       in kernel patch (under review).
    b) Added commands descriptions in devlink-dev man page.

Thanks,
Vikas   


Vikas Gupta (3):
  devlink: update the devlink.h
  devlink: add support for running selftests
  devlink : update man page for new commands

 devlink/devlink.c            | 193 +++++++++++++++++++++++++++++++++++
 include/uapi/linux/devlink.h |  26 +++++
 man/man8/devlink-dev.8       |  46 +++++++++
 3 files changed, 265 insertions(+)

-- 
2.31.1


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]

  parent reply	other threads:[~2022-07-07 18:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 16:44 [PATCH iproute2-next v1 0/2] devlink: add support to run selftests Vikas Gupta
2022-06-28 16:44 ` [PATCH iproute2-next v1 1/2] Update kernel header Vikas Gupta
2022-06-28 16:44 ` [PATCH iproute2-next v1 2/2] devlink: add support for running selftests Vikas Gupta
2022-06-29 11:37 ` [PATCH iproute2-next v1 0/2] devlink: add support to run selftests Ido Schimmel
2022-07-07 18:31 ` Vikas Gupta [this message]
2022-07-07 18:31   ` [PATCH iproute2-next v2 1/3] devlink: update the devlink.h Vikas Gupta
2022-07-07 18:31   ` [PATCH iproute2-next v2 2/3] devlink: add support for running selftests Vikas Gupta
2022-07-07 18:31   ` [PATCH iproute2-next v2 3/3] devlink : update man page for new commands Vikas Gupta
2022-07-10  8:56   ` [PATCH iproute2-next v2 0/3] devlink: add support to run selftests Ido Schimmel
2022-07-18  6:22   ` [PATCH iproute2-next v3 0/3] devlink: add support to run selftest Vikas Gupta
2022-07-18  6:22     ` [PATCH iproute2-next v3 1/3] devlink: update the devlink.h Vikas Gupta
2022-07-18  6:22     ` [PATCH iproute2-next v3 2/3] devlink: add support for running selftests Vikas Gupta
2022-07-18  6:22     ` [PATCH iproute2-next v3 3/3] devlink : update man page and bash-completion for new commands Vikas Gupta

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=20220707183116.29422-1-vikas.gupta@broadcom.com \
    --to=vikas.gupta@broadcom$(echo .)com \
    --cc=andrew.gospodarek@broadcom$(echo .)com \
    --cc=dsahern@kernel$(echo .)org \
    --cc=edumazet@google$(echo .)com \
    --cc=jiri@nvidia$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=michael.chan@broadcom$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=stephen@networkplumber$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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