From: Jiri Pirko <jiri@resnulli.us>
To: alejandro.lucero-palau@amd.com
Cc: netdev@vger.kernel.org, linux-net-drivers@amd.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, habetsm.xilinx@gmail.com,
ecree.xilinx@gmail.com, linux-doc@vger.kernel.org,
corbet@lwn.net, jiri@nvidia.com
Subject: Re: [PATCH v6 net-next 2/8] sfc: add devlink info support for ef100
Date: Wed, 8 Feb 2023 15:38:59 +0100 [thread overview]
Message-ID: <Y+O0A5Bk/zWur76J@nanopsycho> (raw)
In-Reply-To: <20230208142519.31192-3-alejandro.lucero-palau@amd.com>
Wed, Feb 08, 2023 at 03:25:13PM CET, alejandro.lucero-palau@amd.com wrote:
>From: Alejandro Lucero <alejandro.lucero-palau@amd.com>
[..]
>+static int efx_devlink_info_get(struct devlink *devlink,
>+ struct devlink_info_req *req,
>+ struct netlink_ext_ack *extack)
>+{
>+ struct efx_devlink *devlink_private = devlink_priv(devlink);
>+ struct efx_nic *efx = devlink_private->efx;
>+ int rc;
>+
>+ /* Several different MCDI commands are used. We report first error
>+ * through extack along with total number of errors. Specific error
>+ * information via system messages.
I think you forgot to remove this comment.
With this nit fixed, free free to add:
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
>+ */
>+ rc = efx_devlink_info_board_cfg(efx, req);
>+ if (rc) {
>+ NL_SET_ERR_MSG_MOD(extack, "Getting board info failed");
>+ return rc;
>+ }
>+ rc = efx_devlink_info_stored_versions(efx, req);
>+ if (rc) {
>+ NL_SET_ERR_MSG_MOD(extack, "Getting stored versions failed");
>+ return rc;
>+ }
>+ rc = efx_devlink_info_running_versions(efx, req);
>+ if (rc) {
>+ NL_SET_ERR_MSG_MOD(extack, "Getting running versions failed");
>+ return rc;
>+ }
>+
>+ return 0;
>+}
>+#endif
[..]
next prev parent reply other threads:[~2023-02-08 14:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 14:25 [PATCH v6 net-next 0/8] sfc: devlink support for ef100 alejandro.lucero-palau
2023-02-08 14:25 ` [PATCH v6 net-next 1/8] sfc: add " alejandro.lucero-palau
2023-02-10 8:28 ` Martin Habets
2023-02-08 14:25 ` [PATCH v6 net-next 2/8] sfc: add devlink info " alejandro.lucero-palau
2023-02-08 14:38 ` Jiri Pirko [this message]
2023-02-08 15:24 ` Lucero Palau, Alejandro
2023-02-09 10:46 ` Lucero Palau, Alejandro
2023-02-10 11:56 ` Jiri Pirko
2023-02-10 8:40 ` Martin Habets
2023-02-10 9:07 ` Lucero Palau, Alejandro
2023-02-10 15:01 ` Lucero Palau, Alejandro
2023-02-08 14:25 ` [PATCH v6 net-next 3/8] sfc: enumerate mports in ef100 alejandro.lucero-palau
2023-02-10 8:46 ` Martin Habets
2023-02-08 14:25 ` [PATCH v6 net-next 4/8] sfc: add mport lookup based on driver's mport data alejandro.lucero-palau
2023-02-10 8:47 ` Martin Habets
2023-02-08 14:25 ` [PATCH v6 net-next 5/8] sfc: add devlink port support for ef100 alejandro.lucero-palau
2023-02-10 8:49 ` Martin Habets
2023-02-08 14:25 ` [PATCH v6 net-next 6/8] sfc: obtain device mac address based on firmware handle " alejandro.lucero-palau
2023-02-10 8:50 ` Martin Habets
2023-02-08 14:25 ` [PATCH v6 net-next 7/8] sfc: add support for devlink port_function_hw_addr_get in ef100 alejandro.lucero-palau
2023-02-08 14:40 ` Jiri Pirko
2023-02-10 8:52 ` Martin Habets
2023-02-08 14:25 ` [PATCH v6 net-next 8/8] sfc: add support for devlink port_function_hw_addr_set " alejandro.lucero-palau
2023-02-08 14:40 ` Jiri Pirko
2023-02-10 8:53 ` Martin Habets
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=Y+O0A5Bk/zWur76J@nanopsycho \
--to=jiri@resnulli.us \
--cc=alejandro.lucero-palau@amd.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=habetsm.xilinx@gmail.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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