From: Cyrill Gorcunov <gorcunov@gmail.com>
To: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
linux-kernel-list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] USB Elan FTDI: check for driver registration status
Date: Tue, 27 Mar 2007 21:01:25 +0400 [thread overview]
Message-ID: <20070327170125.GA11753@cvg> (raw)
In-Reply-To: <20070327132839.71169aed@localhost>
[Luiz Fernando N. Capitulino - Tue, Mar 27, 2007 at 01:28:39PM -0300]
| Em Tue, 27 Mar 2007 19:14:05 +0400
| Cyrill Gorcunov <gorcunov@gmail.com> escreveu:
|
| | Pete, Luiz
| |
| | what about this one?
| |
| | Actually there is just a check for where is error coming from.
| | Maybe that is not the best solution but it allows us to reduce
| | the calls to 'printk' :)
| |
| | P.S. Pete your patch is good but the message about
| | worqueue creation fail was to print even if we've
| | been faltered on the usb_register procedure.
| |
| | ---
| |
| | drivers/usb/misc/ftdi-elan.c | 15 +++++++++++----
| | 1 files changed, 11 insertions(+), 4 deletions(-)
| |
| | diff --git a/drivers/usb/misc/ftdi-elan.c b/drivers/usb/misc/ftdi-elan.c
| | index bc3327e..3cd54af 100644
| | --- a/drivers/usb/misc/ftdi-elan.c
| | +++ b/drivers/usb/misc/ftdi-elan.c
| | @@ -2903,7 +2903,7 @@ static struct usb_driver ftdi_elan_driver = {
| | };
| | static int __init ftdi_elan_init(void)
| | {
| | - int result;
| | + int result = 0;
| | printk(KERN_INFO "driver %s built at %s on %s\n", ftdi_elan_driver.name,
| | __TIME__, __DATE__);
| | init_MUTEX(&ftdi_module_lock);
| | @@ -2918,18 +2918,25 @@ static int __init ftdi_elan_init(void)
| | if (!respond_queue)
| | goto err3;
| | result = usb_register(&ftdi_elan_driver);
| | - if (result)
| | + if (result) {
| | printk(KERN_ERR "usb_register failed. Error number %d\n",
| | result);
| | + goto err4;
| | + }
| | return result;
| |
| | + err4:
| | + destroy_workqueue(respond_queue);
| | err3:
| | destroy_workqueue(command_queue);
| | err2:
| | destroy_workqueue(status_queue);
| | err1:
| | - printk(KERN_ERR "%s couldn't create workqueue\n", ftdi_elan_driver.name);
| | - return -ENOMEM;
| | + if (result == 0) {
| | + result = -ENOMEM;
| | + printk(KERN_ERR "%s couldn't create workqueue\n", ftdi_elan_driver.name);
| | + }
| | + return result;
| | }
|
| I still the prefer the version I sent you yesterday. :) It
| changes the minimal amount of code.
|
| --
| Luiz Fernando N. Capitulino
|
Liuz,
but the patch you sent me does call
printk(KERN_ERR "%s couldn't create workqueue\n", ftdi_elan_driver.name);
even if error occured in usb_register and that is not good I think.
Fix me if I'm wrong.
Cyrill
next prev parent reply other threads:[~2007-03-27 17:05 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
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 [this message]
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=20070327170125.GA11753@cvg \
--to=gorcunov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=lcapitulino@mandriva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/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