public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Daeseok Youn <daeseok.youn@gmail.com>,
	Mark Hounschell <markh@compro.net>
Cc: lidza.louina@gmail.com, gregkh@linuxfoundation.org,
	devel@driverdev.osuosl.org,
	driverdev-devel@linuxdriverproject.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: dgap: implement error handling in dgap_tty_register()
Date: Fri, 25 Apr 2014 12:26:07 +0300	[thread overview]
Message-ID: <20140425092607.GH26890@mwanda> (raw)
In-Reply-To: <20140425070459.GA9155@devel>

Mark, maybe you should add yourself to the MAINTAINERS entry for this
driver?

On Fri, Apr 25, 2014 at 04:04:59PM +0900, Daeseok Youn wrote:
> @@ -1263,7 +1277,8 @@ static int dgap_tty_register(struct board_t *brd)
>  		/* Register tty devices */
>  		rc = tty_register_driver(brd->SerialDriver);
>  		if (rc < 0)
> -			return rc;
> +			goto free_print_ttys;
> +
>  		brd->dgap_Major_Serial_Registered = TRUE;
>  		dgap_BoardsByMajor[brd->SerialDriver->major] = brd;
>  		brd->dgap_Serial_Major = brd->SerialDriver->major;
> @@ -1273,13 +1288,29 @@ static int dgap_tty_register(struct board_t *brd)
>  		/* Register Transparent Print devices */
>  		rc = tty_register_driver(brd->PrintDriver);
>  		if (rc < 0)
> -			return rc;
> +			goto unregister_serial_drv;
> +
>  		brd->dgap_Major_TransparentPrint_Registered = TRUE;
>  		dgap_BoardsByMajor[brd->PrintDriver->major] = brd;
>  		brd->dgap_TransparentPrint_Major = brd->PrintDriver->major;
>  	}
>  
>  	return rc;
> +
> +unregister_serial_drv:
> +	tty_unregister_driver(brd->SerialDriver);

We only register the ->SerialDriver if someone else hasn't registered it
first?  So this should be:

	if (we_were_the_ones_who_registered_the_serial_driver)
		tty_unregister_driver(brd->SerialDriver);

I haven't followed looked at this.  Who else is registering the serial
driver?  You have looked at this, what do you think?  Or Mark.

regards,
dan carpenter


  reply	other threads:[~2014-04-25  9:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25  7:04 [PATCH] staging: dgap: implement error handling in dgap_tty_register() Daeseok Youn
2014-04-25  9:26 ` Dan Carpenter [this message]
2014-04-25 11:02   ` DaeSeok Youn
     [not found]   ` <875455568.760649.1398423734122.JavaMail.root@mx2.compro.net>
2014-04-25 12:29     ` Mark Hounschell
2014-04-25 12:59       ` Dan Carpenter
     [not found]       ` <1016949935.761818.1398430870736.JavaMail.root@mx2.compro.net>
2014-04-25 14:41         ` Mark Hounschell
2014-04-26  2:39           ` DaeSeok Youn
2014-04-26 18:48             ` Dan Carpenter
2014-04-27 23:21               ` DaeSeok Youn
2014-05-16  9:40                 ` DaeSeok Youn
2014-05-16  9:52                   ` Dan Carpenter
2014-05-16 10:31                     ` DaeSeok Youn
2014-05-16 15:01                     ` Greg KH
2014-05-16 23:09 ` Greg KH
2014-05-17 15:22   ` DaeSeok Youn

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=20140425092607.GH26890@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=daeseok.youn@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=lidza.louina@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markh@compro.net \
    /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