From: "Nelson, Shannon" <shannon.nelson@amd.com>
To: Su Hui <suhui@nfschina.com>,
brett.creeley@amd.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] pds_core: add an error code check in pdsc_dl_info_get
Date: Thu, 19 Oct 2023 08:52:52 -0700 [thread overview]
Message-ID: <c418625c-755f-4e2f-93e7-f2a5d8c7fba3@amd.com> (raw)
In-Reply-To: <20231019083351.1526484-1-suhui@nfschina.com>
On 10/19/2023 1:33 AM, Su Hui wrote:
>
> check the value of 'ret' after call 'devlink_info_version_stored_put'.
>
> Signed-off-by: Su Hui <suhui@nfschina.com>
Thanks.
Reviewed-by: Shannon Nelson <shannon.nelson@amd.com>
> ---
> drivers/net/ethernet/amd/pds_core/devlink.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/net/ethernet/amd/pds_core/devlink.c b/drivers/net/ethernet/amd/pds_core/devlink.c
> index d9607033bbf2..09041f7fccaf 100644
> --- a/drivers/net/ethernet/amd/pds_core/devlink.c
> +++ b/drivers/net/ethernet/amd/pds_core/devlink.c
> @@ -124,6 +124,8 @@ int pdsc_dl_info_get(struct devlink *dl, struct devlink_info_req *req,
> snprintf(buf, sizeof(buf), "fw.slot_%d", i);
> err = devlink_info_version_stored_put(req, buf,
> fw_list.fw_names[i].fw_version);
> + if (err)
> + return err;
> }
>
> err = devlink_info_version_running_put(req,
> --
> 2.30.2
>
next prev parent reply other threads:[~2023-10-19 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 8:33 [PATCH] pds_core: add an error code check in pdsc_dl_info_get Su Hui
2023-10-19 15:52 ` Nelson, Shannon [this message]
2023-10-21 0:50 ` 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=c418625c-755f-4e2f-93e7-f2a5d8c7fba3@amd.com \
--to=shannon.nelson@amd.com \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=suhui@nfschina.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).