public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Salah Triki <salah.triki@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jim Cromie <jim.cromie@gmail.com>, Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: char: scx200_gpio: check return value of cdev_add()
Date: Tue, 15 Apr 2025 16:30:08 +0100	[thread overview]
Message-ID: <Z_57gC8Vb0nPrjO0@pc> (raw)
In-Reply-To: <2025041527-festivity-monitor-6413@gregkh>

On Tue, Apr 15, 2025 at 04:54:38PM +0200, Greg Kroah-Hartman wrote:
> On Mon, Apr 07, 2025 at 05:56:14PM +0100, Salah Triki wrote:
> > Check return value of cdev_add() and in case of error unregister the
> > range of device numbers.
> > 
> > Signed-off-by: Salah Triki <salah.triki@gmail.com>
> > ---
> >  drivers/char/scx200_gpio.c | 6 +++++-
> >  1 file changed, 5 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/char/scx200_gpio.c b/drivers/char/scx200_gpio.c
> > index 700e6affea6f..36efcc828e8e 100644
> > --- a/drivers/char/scx200_gpio.c
> > +++ b/drivers/char/scx200_gpio.c
> > @@ -107,10 +107,14 @@ static int __init scx200_gpio_init(void)
> >  	}
> >  
> >  	cdev_init(&scx200_gpio_cdev, &scx200_gpio_fileops);
> > -	cdev_add(&scx200_gpio_cdev, devid, MAX_PINS);
> > +	rc = cdev_add(&scx200_gpio_cdev, devid, MAX_PINS);
> > +	if (rc)
> > +		goto unregister_chrdev_region;
> >  
> >  	return 0; /* succeed */
> >  
> > +unregister_chrdev_region:
> > +	unregister_chrdev_region(devid, MAX_PINS);
> >  undo_platform_device_add:
> >  	platform_device_del(pdev);
> >  undo_malloc:
> > -- 
> > 2.43.0
> > 
> 
> How was this tested?
> 

I only compiled it.

ST 

> thanks,
> 
> greg k-h

  reply	other threads:[~2025-04-15 15:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 16:56 [PATCH] drivers: char: scx200_gpio: check return value of cdev_add() Salah Triki
2025-04-15 14:54 ` Greg Kroah-Hartman
2025-04-15 15:30   ` Salah Triki [this message]
2025-04-15 16:01     ` Greg Kroah-Hartman

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=Z_57gC8Vb0nPrjO0@pc \
    --to=salah.triki@gmail.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jim.cromie@gmail.com \
    --cc=linux-kernel@vger.kernel.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