public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
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 11/15] staging: gpib: ines: Handle gpib_register_driver() errors
Date: Sun, 29 Dec 2024 11:28:10 +0100	[thread overview]
Message-ID: <2024122943-fervor-unhinge-0ed2@gregkh> (raw)
In-Reply-To: <20241228060800.107653-12-niharchaithanya@gmail.com>

On Sat, Dec 28, 2024 at 11:37:59AM +0530, Nihar Chaithanya wrote:
> The function ines_pcmcia_init_module() can be replaced by calling
> pcmcia_register_driver() directly. The error value from this
> function is not returned and the previous registering functions
> are not unregistered.
> 
> The function gpib_register_driver() can fail and similar to
> pcmcia_register_driver() function failing, the previous registering
> functions are not unregistered.
> 
> Replace cb_pcmcia_init_module() with pcmcia_register_driver().
> Unregister the gpib and pci register functions if the subsequent
> gpib or pcmcia register functions fail and return the error value.
> 
> Signed-off-by: Nihar Chaithanya <niharchaithanya@gmail.com>
> ---
>  drivers/staging/gpib/ines/ines_gpib.c | 81 ++++++++++++++++++++-------
>  1 file changed, 60 insertions(+), 21 deletions(-)
> 
> diff --git a/drivers/staging/gpib/ines/ines_gpib.c b/drivers/staging/gpib/ines/ines_gpib.c
> index 9d8387c3bf01..73df4cd16926 100644
> --- a/drivers/staging/gpib/ines/ines_gpib.c
> +++ b/drivers/staging/gpib/ines/ines_gpib.c
> @@ -1227,12 +1227,6 @@ static struct pcmcia_driver ines_gpib_cs_driver = {
>  	.resume		= ines_gpib_resume,
>  };
>  
> -int ines_pcmcia_init_module(void)
> -{
> -	pcmcia_register_driver(&ines_gpib_cs_driver);
> -	return 0;
> -}
> -
>  void ines_pcmcia_cleanup_module(void)
>  {
>  	DEBUG(0, "ines_cs: unloading\n");
> @@ -1420,28 +1414,73 @@ void ines_pcmcia_detach(gpib_board_t *board)
>  
>  static int __init ines_init_module(void)
>  {
> -	int err = 0;
> +	int ret;
>  
> -	err = pci_register_driver(&ines_pci_driver);
> -	if (err) {
> -		pr_err("ines_gpib: pci_driver_register failed!\n");
> -		return err;
> +	ret = pci_register_driver(&ines_pci_driver);
> +	if (ret) {
> +		pr_err("ines_gpib: pci_driver_register failed: error = %d\n", ret);
> +		return ret;
>  	}
>  
> -	gpib_register_driver(&ines_pci_interface, THIS_MODULE);
> -	gpib_register_driver(&ines_pci_unaccel_interface, THIS_MODULE);
> -	gpib_register_driver(&ines_pci_accel_interface, THIS_MODULE);
> -	gpib_register_driver(&ines_isa_interface, THIS_MODULE);
> +	ret = gpib_register_driver(&ines_pci_interface, THIS_MODULE);
> +	if (ret)
> +		goto err_pci;
> +
> +	ret = gpib_register_driver(&ines_pci_unaccel_interface, THIS_MODULE);
> +	if (ret)
> +		goto err_pci_unaccel;
> +
> +	ret = gpib_register_driver(&ines_pci_accel_interface, THIS_MODULE);
> +	if (ret)
> +		goto err_pci_accel;
> +
> +	ret = gpib_register_driver(&ines_isa_interface, THIS_MODULE);
> +	if (ret)
> +		goto err_isa;
> +
>  #ifdef GPIB_PCMCIA
> -	gpib_register_driver(&ines_pcmcia_interface, THIS_MODULE);
> -	gpib_register_driver(&ines_pcmcia_unaccel_interface, THIS_MODULE);
> -	gpib_register_driver(&ines_pcmcia_accel_interface, THIS_MODULE);
> -	err += ines_pcmcia_init_module();
> +	ret = gpib_register_driver(&ines_pcmcia_interface, THIS_MODULE);
> +	if (ret)
> +		goto err_pcmcia;
> +
> +	ret = gpib_register_driver(&ines_pcmcia_unaccel_interface, THIS_MODULE);
> +	if (ret)
> +		goto err_pcmcia_unaccel;
> +
> +	ret = gpib_register_driver(&ines_pcmcia_accel_interface, THIS_MODULE);
> +	if (ret)
> +		goto err_pcmcia_accel;
> +
> +	ret = pcmcia_register_driver(&ines_gpib_cs_driver);
> +	if (ret)
> +		goto err_pcmcia_driver;
>  #endif
> -	if (err)
> -		return -1;
>  
> +	pr_info("ines_gpib: module init is complete\n");

Why did you add this debugging line here that was not here at all?

>  	return 0;
> +
> +#ifdef GPIB_PCMCIA
> +err_pcmcia_driver:
> +	pr_err("ines_gpib: pcmcia_register_driver failed: error = %d\n", ret);

Why just this error message for only this one failure?

> +	gpib_unregister_driver(&ines_pcmcia_accel_interface);
> +err_pcmcia_accel:
> +	gpib_unregister_driver(&ines_pcmcia_unaccel_interface);
> +err_pcmcia_unaccel:
> +	gpib_unregister_driver(&ines_pcmcia_interface);
> +err_pcmcia:
> +#endif
> +	gpib_unregister_driver(&ines_isa_interface);
> +err_isa:
> +	gpib_unregister_driver(&ines_pci_accel_interface);
> +err_pci_accel:
> +	gpib_unregister_driver(&ines_pci_unaccel_interface);
> +err_pci_unaccel:
> +	gpib_unregister_driver(&ines_pci_interface);
> +err_pci:
> +	pci_unregister_driver(&ines_pci_driver);
> +
> +	pr_err("ines_gpib: gpib_register_driver failed!\n");

Why not provide the error number here too?

thanks,

greg k-h

  reply	other threads:[~2024-12-29 10:28 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
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 [this message]
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=2024122943-fervor-unhinge-0ed2@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