From: Hans de Goede <hdegoede@redhat.com>
To: Vadim Pasternak <vadimp@nvidia.com>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH platform-next 1/1] platform/mellanox: mlxreg-lc: Make error handling flow consistent
Date: Fri, 9 Sep 2022 19:51:28 +0200 [thread overview]
Message-ID: <f98cc079-3ded-e8aa-da27-62fd298b79ca@redhat.com> (raw)
In-Reply-To: <20220904141113.49048-1-vadimp@nvidia.com>
Hi,
On 9/4/22 16:11, Vadim Pasternak wrote:
> Use 'goto' statement in error flow of mlxreg_lc_event_handler() at all
> places for consistency.
>
> This follow-up patch implementing comments from
> https://www.spinics.net/lists/platform-driver-x86/msg34587.html
>
> Signed-off-by: Vadim Pasternak <vadimp@nvidia.com>
> ---
> drivers/platform/mellanox/mlxreg-lc.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/platform/mellanox/mlxreg-lc.c b/drivers/platform/mellanox/mlxreg-lc.c
> index 1e071df4c9f5..d47fe22080e6 100644
> --- a/drivers/platform/mellanox/mlxreg-lc.c
> +++ b/drivers/platform/mellanox/mlxreg-lc.c
> @@ -564,10 +564,8 @@ static int mlxreg_lc_event_handler(void *handle, enum mlxreg_hotplug_kind kind,
> mlxreg_lc->data->slot, mlxreg_lc->state, kind, action);
>
> mutex_lock(&mlxreg_lc->lock);
> - if (!(mlxreg_lc->state & MLXREG_LC_INITIALIZED)) {
> - mutex_unlock(&mlxreg_lc->lock);
> - return 0;
> - }
> + if (!(mlxreg_lc->state & MLXREG_LC_INITIALIZED))
> + goto mlxreg_lc_non_initialzed_exit;
>
> switch (kind) {
> case MLXREG_HOTPLUG_LC_SYNCED:
> @@ -594,8 +592,7 @@ static int mlxreg_lc_event_handler(void *handle, enum mlxreg_hotplug_kind kind,
> /* In case line card is configured - enable it. */
> if (mlxreg_lc->state & MLXREG_LC_CONFIGURED)
> err = mlxreg_lc_enable_disable(mlxreg_lc, 1);
> - mutex_unlock(&mlxreg_lc->lock);
> - return err;
> + goto mlxreg_lc_enable_disable_exit;
The intend of this goto is wrong (one indent level too much).
I have merged this now with the indent fixed up:
Thank you for your patch, I've applied this patch to my review-hans
branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
Note it will show up in my review-hans branch once I've pushed my
local branch there, which might take a while.
Once I've run some tests on this branch the patches there will be
added to the platform-drivers-x86/for-next branch and eventually
will be included in the pdx86 pull-request to Linus for the next
merge-window.
Regards,
Hans
> }
> err = mlxreg_lc_create_static_devices(mlxreg_lc, mlxreg_lc->main_devs,
> mlxreg_lc->main_devs_num);
> @@ -627,8 +624,10 @@ static int mlxreg_lc_event_handler(void *handle, enum mlxreg_hotplug_kind kind,
> break;
> }
>
> +mlxreg_lc_enable_disable_exit:
> mlxreg_lc_power_on_off_fail:
> mlxreg_lc_create_static_devices_fail:
> +mlxreg_lc_non_initialzed_exit:
> mutex_unlock(&mlxreg_lc->lock);
>
> return err;
prev parent reply other threads:[~2022-09-09 17:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 14:11 [PATCH platform-next 1/1] platform/mellanox: mlxreg-lc: Make error handling flow consistent Vadim Pasternak
2022-09-09 17:51 ` Hans de Goede [this message]
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=f98cc079-3ded-e8aa-da27-62fd298b79ca@redhat.com \
--to=hdegoede@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=vadimp@nvidia.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