From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>,
Wei-Ning Huang <wnhuang@google.com>
Subject: Re: [PATCH 3/3] firmware: vpd: Fix platform driver and device registration/unregistration
Date: Wed, 15 Nov 2017 14:28:37 -0800 [thread overview]
Message-ID: <20171115222837.ani36g2zeujsia6e@dtor-ws> (raw)
In-Reply-To: <1510779645-13052-3-git-send-email-linux@roeck-us.net>
On Wed, Nov 15, 2017 at 01:00:45PM -0800, Guenter Roeck wrote:
> The driver exit function needs to unregister both platform device and
> driver. Also, during registration, register driver first and perform
> error checks.
>
> Fixes: 049a59db34eb ("firmware: Google VPD sysfs driver")
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Reviewed-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> ---
> drivers/firmware/google/vpd.c | 18 +++++++++++++-----
> 1 file changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/firmware/google/vpd.c b/drivers/firmware/google/vpd.c
> index 942e358efa60..e4b40f2b4627 100644
> --- a/drivers/firmware/google/vpd.c
> +++ b/drivers/firmware/google/vpd.c
> @@ -326,21 +326,29 @@ static struct platform_driver vpd_driver = {
> },
> };
>
> +static struct platform_device *vpd_pdev;
> +
> static int __init vpd_platform_init(void)
> {
> - struct platform_device *pdev;
> + int ret;
>
> - pdev = platform_device_register_simple("vpd", -1, NULL, 0);
> - if (IS_ERR(pdev))
> - return PTR_ERR(pdev);
> + ret = platform_driver_register(&vpd_driver);
> + if (ret)
> + return ret;
>
> - platform_driver_register(&vpd_driver);
> + vpd_pdev = platform_device_register_simple("vpd", -1, NULL, 0);
> + if (IS_ERR(vpd_pdev)) {
> + platform_driver_unregister(&vpd_driver);
> + return PTR_ERR(vpd_pdev);
> + }
>
> return 0;
> }
>
> static void __exit vpd_platform_exit(void)
> {
> + platform_device_unregister(vpd_pdev);
> + platform_driver_unregister(&vpd_driver);
> }
>
> module_init(vpd_platform_init);
> --
> 2.7.4
>
--
Dmitry
next prev parent reply other threads:[~2017-11-15 22:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 21:00 [PATCH 1/3] firmware: vpd: Destroy vpd sections in remove function Guenter Roeck
2017-11-15 21:00 ` [PATCH 2/3] firmware: vpd: Tie firmware kobject to device lifetime Guenter Roeck
2017-11-15 22:28 ` Dmitry Torokhov
2017-11-15 21:00 ` [PATCH 3/3] firmware: vpd: Fix platform driver and device registration/unregistration Guenter Roeck
2017-11-15 22:28 ` Dmitry Torokhov [this message]
2017-11-15 22:27 ` [PATCH 1/3] firmware: vpd: Destroy vpd sections in remove function Dmitry Torokhov
2017-11-16 1:08 ` Randy Dunlap
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=20171115222837.ani36g2zeujsia6e@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rdunlap@infradead.org \
--cc=wnhuang@google.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
all inboxes | Powered by JetHome®