From: Jiri Pirko <jiri@resnulli•us>
To: Vikas Gupta <vikas.gupta@broadcom•com>
Cc: jiri@nvidia•com, kuba@kernel•org, netdev@vger•kernel.org,
linux-kernel@vger•kernel.org, davem@davemloft•net,
dsahern@kernel•org, stephen@networkplumber•org,
edumazet@google•com, pabeni@redhat•com, ast@kernel•org,
leon@kernel•org, linux-doc@vger•kernel.org, corbet@lwn•net,
michael.chan@broadcom•com, andrew.gospodarek@broadcom•com
Subject: Re: [PATCH net-next v9 2/2] bnxt_en: implement callbacks for devlink selftests
Date: Thu, 28 Jul 2022 10:53:10 +0200 [thread overview]
Message-ID: <YuJOdsgzqlzPAZZn@nanopsycho> (raw)
In-Reply-To: <20220727165721.37959-3-vikas.gupta@broadcom.com>
Wed, Jul 27, 2022 at 06:57:21PM CEST, vikas.gupta@broadcom•com wrote:
>From: vikas <vikas.gupta@broadcom•com>
>
>Add callbacks
>=============
>.selftest_check: returns true for flash selftest.
>.selftest_run: runs a flash selftest.
>
>Also, refactor NVM APIs so that they can be
>used with devlink and ethtool both.
>
>Signed-off-by: Vikas Gupta <vikas.gupta@broadcom•com>
Reviewed-by: Jiri Pirko <jiri@nvidia•com>
next prev parent reply other threads:[~2022-07-28 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 16:57 [PATCH net-next v9 0/2] add framework for selftests in devlink Vikas Gupta
2022-07-27 16:57 ` [PATCH net-next v9 1/2] devlink: introduce framework for selftests Vikas Gupta
2022-07-27 17:19 ` Andy Gospodarek
2022-07-28 8:52 ` Jiri Pirko
2022-07-27 16:57 ` [PATCH net-next v9 2/2] bnxt_en: implement callbacks for devlink selftests Vikas Gupta
2022-07-27 17:20 ` Andy Gospodarek
2022-07-28 8:53 ` Jiri Pirko [this message]
2022-07-28 8:52 ` [PATCH net-next v9 0/2] add framework for selftests in devlink Jiri Pirko
2022-07-29 5:30 ` 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=YuJOdsgzqlzPAZZn@nanopsycho \
--to=jiri@resnulli$(echo .)us \
--cc=andrew.gospodarek@broadcom$(echo .)com \
--cc=ast@kernel$(echo .)org \
--cc=corbet@lwn$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=jiri@nvidia$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=leon@kernel$(echo .)org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=michael.chan@broadcom$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=stephen@networkplumber$(echo .)org \
--cc=vikas.gupta@broadcom$(echo .)com \
/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