From: Jiri Pirko <jiri@nvidia.com>
To: Vikas Gupta <vikas.gupta@broadcom.com>
Cc: 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 v4 1/3] devlink: introduce framework for selftests
Date: Thu, 21 Jul 2022 15:01:28 +0200 [thread overview]
Message-ID: <YtlOKP4i3AG0gz+B@nanopsycho> (raw)
In-Reply-To: <20220721072121.43648-2-vikas.gupta@broadcom.com>
Thu, Jul 21, 2022 at 09:21:19AM CEST, vikas.gupta@broadcom.com wrote:
[...]
>+ /**
>+ * selftest_run() - Runs a selftest
>+ * @devlink: Devlink instance
>+ * @test_id: test index
>+ * @extack: extack for reporting error messages
>+ *
>+ * Return: Result of the test
>+ */
>+ u8 (*selftest_run)(struct devlink *devlink, int test_id,
It should return enum. Make sure you changed the variable type you store
the test status in.
>+ struct netlink_ext_ack *extack);
> };
[...]
next prev parent reply other threads:[~2022-07-21 13:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0220707182950.29348-1-vikas.gupta@broadcom.com>
2022-07-18 6:20 ` [PATCH net-next v3 0/3] add framework for selftests in devlink Vikas Gupta
2022-07-18 6:20 ` [PATCH net-next v3 1/3] devlink: introduce framework for selftests Vikas Gupta
2022-07-19 3:33 ` Jakub Kicinski
2022-07-19 10:18 ` Vikas Gupta
2022-07-18 6:20 ` [PATCH net-next v3 2/3] bnxt_en: refactor NVM APIs Vikas Gupta
2022-07-18 6:20 ` [PATCH net-next v3 3/3] bnxt_en: implement callbacks for devlink selftests Vikas Gupta
2022-07-21 7:21 ` [PATCH net-next v4 0/3] add framework for selftests in devlink Vikas Gupta
2022-07-21 7:21 ` [PATCH net-next v4 1/3] devlink: introduce framework for selftests Vikas Gupta
2022-07-21 12:56 ` Jiri Pirko
2022-07-21 17:32 ` Vikas Gupta
2022-07-22 6:41 ` Jiri Pirko
2022-07-21 13:01 ` Jiri Pirko [this message]
2022-07-21 7:21 ` [PATCH net-next v4 2/3] bnxt_en: refactor NVM APIs Vikas Gupta
2022-07-21 13:02 ` Jiri Pirko
2022-07-21 14:24 ` Vikas Gupta
2022-07-21 7:21 ` [PATCH net-next v4 3/3] bnxt_en: implement callbacks for devlink selftests Vikas Gupta
2022-07-21 12:59 ` Jiri Pirko
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=YtlOKP4i3AG0gz+B@nanopsycho \
--to=jiri@nvidia.com \
--cc=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=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;
as well as URLs for NNTP newsgroup(s).