From: Cyrill Gorcunov <gorcunov@gmail.com>
To: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
Cc: linux-kernel-list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] USB Elan FTDI: check for driver registration status
Date: Mon, 26 Mar 2007 23:33:12 +0400 [thread overview]
Message-ID: <20070326193312.GA10296@cvg> (raw)
In-Reply-To: <20070326154357.025e4faf@localhost>
[Luiz Fernando N. Capitulino - Mon, Mar 26, 2007 at 03:43:57PM -0300]
|
| Hi Cyrill,
|
| Em Sun, 25 Mar 2007 11:27:33 +0400
| Cyrill Gorcunov <gorcunov@gmail.com> escreveu:
|
| | This patch adds checking of driver registration status
| | and if it fails release allocated resources.
| |
| | Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
| |
| | ---
| |
| | Pete, please review the patch and Ack it then.
| |
| | drivers/usb/misc/ftdi-elan.c | 37 +++++++++++++++++++++++--------------
| | 1 files changed, 23 insertions(+), 14 deletions(-)
| |
| | diff --git a/drivers/usb/misc/ftdi-elan.c b/drivers/usb/misc/ftdi-elan.c
| | index bc3327e..3cd9ae3 100644
| | --- a/drivers/usb/misc/ftdi-elan.c
| | +++ b/drivers/usb/misc/ftdi-elan.c
| | @@ -2909,27 +2909,36 @@ static int __init ftdi_elan_init(void)
| | init_MUTEX(&ftdi_module_lock);
| | INIT_LIST_HEAD(&ftdi_static_list);
| | status_queue = create_singlethread_workqueue("ftdi-status-control");
| | - if (!status_queue)
| | - goto err1;
| | command_queue = create_singlethread_workqueue("ftdi-command-engine");
| | - if (!command_queue)
| | - goto err2;
| | respond_queue = create_singlethread_workqueue("ftdi-respond-engine");
| | - if (!respond_queue)
| | - goto err3;
| | + if (!status_queue || !command_queue || !respond_queue) {
| | + printk(KERN_ERR "%s couldn't create workqueue\n",
| | + ftdi_elan_driver.name);
| | + result = -ENOMEM;
| | + goto err;
| | + }
|
| The current version looks ok to me, why are you changing it?
|
| It's also smater, ie, if the first workqueue creation fails, it
| won't try to create the others.
|
| | result = usb_register(&ftdi_elan_driver);
| | - if (result)
| | + if (result) {
| | printk(KERN_ERR "usb_register failed. Error number %d\n",
| | result);
| | + goto err;
| | + }
| | return result;
|
| This could be:
|
| """
| if (result) {
| printk(KERN_ERR "usb_register failed. Error number %d\n",
| result);
| destroy_workqueue(respond_queue);
| goto err3;
| }
| """
|
| And you can change 'err1' to return 'result'.
|
| --
| Luiz Fernando N. Capitulino
|
Hi Luiz,
if usb registration failed we should release all worqueues we've
created and that is the reason why I've changed the code...
but anyway I have to find more elegant solution I think :)
Cyrill
next prev parent reply other threads:[~2007-03-26 19:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 7:27 [PATCH] USB Elan FTDI: check for driver registration status Cyrill Gorcunov
2007-03-26 18:43 ` Luiz Fernando N. Capitulino
2007-03-26 19:33 ` Cyrill Gorcunov [this message]
2007-03-26 19:56 ` Luiz Fernando N. Capitulino
2007-03-28 16:00 ` Cyrill Gorcunov
2007-03-28 18:41 ` Pete Zaitcev
2007-03-26 22:17 ` Pete Zaitcev
2007-03-27 15:14 ` Cyrill Gorcunov
2007-03-27 16:28 ` Luiz Fernando N. Capitulino
2007-03-27 17:01 ` Cyrill Gorcunov
2007-03-27 17:29 ` Luiz Fernando N. Capitulino
2007-03-27 17:37 ` Cyrill Gorcunov
2007-03-27 17:51 ` Pete Zaitcev
2007-03-27 18:16 ` Cyrill Gorcunov
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=20070326193312.GA10296@cvg \
--to=gorcunov@gmail.com \
--cc=lcapitulino@mandriva.com.br \
--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