From: Greg KH <gregkh@linuxfoundation.org>
To: Yuan Can <yuancan@huawei.com>
Cc: tzungbi@kernel.org, briannorris@chromium.org,
jwerner@chromium.org, adurbin@chromium.org, furquan@chromium.org,
rajatja@chromium.org, groeck@chromium.org,
chrome-platform@lists.linux.dev
Subject: Re: [PATCH] firmware: google: Unregister driver_info on failure
Date: Tue, 15 Oct 2024 19:15:53 +0200 [thread overview]
Message-ID: <2024101544-defender-rename-4607@gregkh> (raw)
In-Reply-To: <20241015131344.20272-1-yuancan@huawei.com>
On Tue, Oct 15, 2024 at 09:13:44PM +0800, Yuan Can wrote:
> When platform_device_register_full() returns error, the gsmi_init() returns
> without unregister gsmi_driver_info, fix by add missing
> platform_driver_unregister() when platform_device_register_full() failed.
>
> Fixes: 8942b2d5094b ("gsmi: Add GSMI commands to log S0ix info")
> Signed-off-by: Yuan Can <yuancan@huawei.com>
> ---
> drivers/firmware/google/gsmi.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/firmware/google/gsmi.c b/drivers/firmware/google/gsmi.c
> index d304913314e4..24e666d5c3d1 100644
> --- a/drivers/firmware/google/gsmi.c
> +++ b/drivers/firmware/google/gsmi.c
> @@ -918,7 +918,8 @@ static __init int gsmi_init(void)
> gsmi_dev.pdev = platform_device_register_full(&gsmi_dev_info);
> if (IS_ERR(gsmi_dev.pdev)) {
> printk(KERN_ERR "gsmi: unable to register platform device\n");
> - return PTR_ERR(gsmi_dev.pdev);
> + ret = PTR_ERR(gsmi_dev.pdev);
> + goto out_unregister;
> }
>
> /* SMI access needs to be serialized */
> @@ -1056,10 +1057,11 @@ static __init int gsmi_init(void)
> gsmi_buf_free(gsmi_dev.name_buf);
> kmem_cache_destroy(gsmi_dev.mem_pool);
> platform_device_unregister(gsmi_dev.pdev);
> - pr_info("gsmi: failed to load: %d\n", ret);
> +out_unregister:
> #ifdef CONFIG_PM
> platform_driver_unregister(&gsmi_driver_info);
> #endif
> + pr_info("gsmi: failed to load: %d\n", ret);
> return ret;
> }
>
> --
> 2.17.1
>
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- You have marked a patch with a "Fixes:" tag for a commit that is in an
older released kernel, yet you do not have a cc: stable line in the
signed-off-by area at all, which means that the patch will not be
applied to any older kernel releases. To properly fix this, please
follow the documented rules in the
Documentation/process/stable-kernel-rules.rst file for how to resolve
this.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
next prev parent reply other threads:[~2024-10-15 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 13:13 [PATCH] firmware: google: Unregister driver_info on failure Yuan Can
2024-10-15 17:15 ` Greg KH [this message]
2024-10-15 21:28 ` Brian Norris
2024-10-15 22:54 ` Tzung-Bi Shih
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=2024101544-defender-rename-4607@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=adurbin@chromium.org \
--cc=briannorris@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=furquan@chromium.org \
--cc=groeck@chromium.org \
--cc=jwerner@chromium.org \
--cc=rajatja@chromium.org \
--cc=tzungbi@kernel.org \
--cc=yuancan@huawei.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