From: Greg KH <gregkh@linuxfoundation.org>
To: Nihar Chaithanya <niharchaithanya@gmail.com>
Cc: dpenkler@gmail.com, dan.carpenter@linaro.org,
skhan@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 02/15] staging: gpib: agilent_82350b: Handle gpib_register_driver() errors
Date: Sun, 29 Dec 2024 11:29:03 +0100 [thread overview]
Message-ID: <2024122926-size-playset-70c0@gregkh> (raw)
In-Reply-To: <20241228060800.107653-3-niharchaithanya@gmail.com>
On Sat, Dec 28, 2024 at 11:37:50AM +0530, Nihar Chaithanya wrote:
> The function gpib_register_driver() can fail which can result in
> semi-registered module.
>
> In case gpib_register_driver() fails unregister the previous
> gpib and pci registering functions, return the error value.
>
> Signed-off-by: Nihar Chaithanya <niharchaithanya@gmail.com>
> ---
> .../gpib/agilent_82350b/agilent_82350b.c | 21 ++++++++++++++++---
> 1 file changed, 18 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/gpib/agilent_82350b/agilent_82350b.c b/drivers/staging/gpib/agilent_82350b/agilent_82350b.c
> index 53006d0cc79c..6f077ede86a6 100644
> --- a/drivers/staging/gpib/agilent_82350b/agilent_82350b.c
> +++ b/drivers/staging/gpib/agilent_82350b/agilent_82350b.c
> @@ -910,13 +910,28 @@ static int __init agilent_82350b_init_module(void)
>
> result = pci_register_driver(&agilent_82350b_pci_driver);
> if (result) {
> - pr_err("agilent_82350b: pci_driver_register failed!\n");
> + pr_err("agilent_82350b: pci_driver_register failed: error = %d\n", result);
> return result;
> }
>
> - gpib_register_driver(&agilent_82350b_unaccel_interface, THIS_MODULE);
> - gpib_register_driver(&agilent_82350b_interface, THIS_MODULE);
> + result = gpib_register_driver(&agilent_82350b_unaccel_interface, THIS_MODULE);
> + if (result)
> + goto err_unaccel;
> +
> + result = gpib_register_driver(&agilent_82350b_interface, THIS_MODULE);
> + if (result)
> + goto err_interface;
> +
> + pr_info("agilent_82350b: module init is complete\n");
Why are you adding noise to drivers like this? When drivers work
properly, they are quiet.
> return 0;
> +
> +err_interface:
> + gpib_unregister_driver(&agilent_82350b_unaccel_interface);
> +err_unaccel:
> + pci_unregister_driver(&agilent_82350b_pci_driver);
> +
> + pr_err("agilent_82350b: gpib_register_driver failed!\n");
No error number here?
Same for all the other changes in this series.
thanks,
greg k-h
next prev parent reply other threads:[~2024-12-29 10:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-28 6:07 [PATCH v5 00/15] staging: gpib: Handle gpib_register_driver() errors Nihar Chaithanya
2024-12-28 6:07 ` [PATCH v5 01/15] staging: gpib: Modify gpib_register_driver() to return error if it fails Nihar Chaithanya
2024-12-29 10:30 ` Greg KH
2024-12-28 6:07 ` [PATCH v5 02/15] staging: gpib: agilent_82350b: Handle gpib_register_driver() errors Nihar Chaithanya
2024-12-29 10:29 ` Greg KH [this message]
2024-12-28 6:07 ` [PATCH v5 03/15] staging: gpib: agilent_82357a: " Nihar Chaithanya
2024-12-28 6:07 ` [PATCH v5 04/15] staging: gpib: cb7210: " Nihar Chaithanya
2024-12-28 6:07 ` [PATCH v5 05/15] staging: gpib: cec: " Nihar Chaithanya
2024-12-28 6:07 ` [PATCH v5 06/15] staging: gpib: fluke: " Nihar Chaithanya
2024-12-28 6:07 ` [PATCH v5 07/15] staging: gpib: fmh: " Nihar Chaithanya
2024-12-28 9:24 ` kernel test robot
2024-12-28 6:07 ` [PATCH v5 08/15] staging: gpib: gpio: Return error value from gpib_register_driver() Nihar Chaithanya
2024-12-28 6:07 ` [PATCH v5 09/15] staging: gpib: hp_82335: " Nihar Chaithanya
2024-12-28 6:07 ` [PATCH v5 10/15] staging: gpib: hp_82341: Handle gpib_register_driver() errors Nihar Chaithanya
2024-12-28 6:07 ` [PATCH v5 11/15] staging: gpib: ines: " Nihar Chaithanya
2024-12-29 10:28 ` Greg KH
2024-12-29 10:46 ` Nihar Chaithanya
2024-12-28 6:08 ` [PATCH v5 12/15] staging: gpib: lpvo_usb: Return error value from gpib_register_driver() Nihar Chaithanya
2024-12-28 6:08 ` [PATCH v5 13/15] staging: gpib: ni_usb: Handle gpib_register_driver() errors Nihar Chaithanya
2024-12-28 6:08 ` [PATCH v5 14/15] staging: gpib: pc2: " Nihar Chaithanya
2024-12-28 6:08 ` [PATCH v5 15/15] staging: gpib: tnt4882: " Nihar Chaithanya
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=2024122926-size-playset-70c0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@linaro.org \
--cc=dpenkler@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=niharchaithanya@gmail.com \
--cc=skhan@linuxfoundation.org \
/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