From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [PATCH 2/10] sysdev: add error check in sysdev_register()
Date: Mon, 16 Jul 2007 17:12:34 +0200 [thread overview]
Message-ID: <20070716171234.2bc31be8@gondolin.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20070716135138.GB2040@APFDCB5C>
On Mon, 16 Jul 2007 22:51:38 +0900,
Akinobu Mita <akinobu.mita@gmail.com> wrote:
> This patch enables to catch the errors returned by add() procedure of
> sysdev driver in sysdev_register.
> @@ -253,23 +254,50 @@ int sysdev_register(struct sys_device *
>
> /* Notify global drivers */
> list_for_each_entry(drv, &sysdev_drivers, entry) {
> - if (drv->add)
> - drv->add(sysdev);
> + if (drv->add) {
> + error = drv->add(sysdev);
> + if (error)
> + goto error_sysdev;
> + }
> + added_sysdev++;
> }
This looks asymmetric to me. Imagine we have a device/driver
combination for which drv->add will return -ESOMEERROR. Now, it depends
on the order:
1. The device is registered when the driver is already registered:
registration of the device will fail.
2. The driver is registered when the device is already registered:
driver registration will succeed, and the device will stay registered.
I'm not sure if that is what we really want.
next prev parent reply other threads:[~2007-07-16 15:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 13:48 [PATCH 0/10] CPU hotplug error handling fixes Akinobu Mita
2007-07-16 13:50 ` [PATCH 1/10] sysfs: fix kmem_cache_free(NULL) Akinobu Mita
2007-07-16 15:43 ` Greg KH
2007-07-16 16:53 ` Akinobu Mita
2007-07-17 7:04 ` Pekka J Enberg
2007-07-16 13:51 ` [PATCH 2/10] sysdev: add error check in sysdev_register() Akinobu Mita
2007-07-16 15:12 ` Cornelia Huck [this message]
2007-07-16 16:18 ` Akinobu Mita
2007-07-16 13:52 ` [PATCH 3/10] sysfs: fix error handling in create_files() Akinobu Mita
2007-07-16 15:29 ` Cornelia Huck
2007-07-16 16:28 ` Akinobu Mita
2007-07-16 16:29 ` Greg KH
2007-07-17 16:22 ` Akinobu Mita
2007-07-16 13:53 ` [PATCH 4/10] cpu: deliver CPU_UP_CANCELED only to NOTIFY_OKed callbacks with CPU_UP_PREPARE Akinobu Mita
2007-07-17 8:23 ` Gautham R Shenoy
2007-07-17 17:18 ` Akinobu Mita
2007-07-18 6:54 ` Gautham R Shenoy
2007-07-18 16:28 ` Akinobu Mita
2007-07-16 13:54 ` [PATCH 5/10] topology: remove topology_dev_map Akinobu Mita
2007-07-16 13:57 ` [PATCH 6/10] thermal_throttle: fix cpu hotplug error handling Akinobu Mita
2007-07-16 13:58 ` [PATCH 7/10] msr: " Akinobu Mita
2007-07-16 13:58 ` [PATCH 8/10] cpuid: " Akinobu Mita
2007-07-16 14:00 ` [PATCH 9/10] mce: " Akinobu Mita
2007-07-16 14:01 ` [PATCH 10/10] intel_cacheinfo: " Akinobu Mita
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=20070716171234.2bc31be8@gondolin.boeblingen.de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=akinobu.mita@gmail.com \
--cc=gregkh@suse.de \
--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
all inboxes | Powered by JetHome®