From: Andy Gospodarek <andrew.gospodarek@broadcom.com>
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: Wed, 27 Jul 2022 13:20:35 -0400 [thread overview]
Message-ID: <YuFz488QqY3L1PxF@C02YVCJELVCG.dhcp.broadcom.net> (raw)
In-Reply-To: <20220727165721.37959-3-vikas.gupta@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
On Wed, Jul 27, 2022 at 10:27:21PM +0530, Vikas Gupta 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: Andy Gospodarek <gospo@broadcom.com>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4222 bytes --]
next prev parent reply other threads:[~2022-07-27 18:21 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 [this message]
2022-07-28 8:53 ` Jiri Pirko
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=YuFz488QqY3L1PxF@C02YVCJELVCG.dhcp.broadcom.net \
--to=andrew.gospodarek@broadcom.com \
--cc=ast@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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
all inboxes | Powered by JetHome®