From: Jarek Poplawski <jarkao2@gmail.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: Greg KH <gregkh@suse.de>,
stefanr@s5r6.in-berlin.de, James.Bottomley@hansenpartnership.com,
a.zummo@towertech.it, peterz@infradead.org, cbou@mail.ru,
linux-kernel@vger.kernel.org,
David Brownell <david-b@pacbell.net>,
krh@redhat.com, stern@rowland.harvard.edu, dwmw2@infradead.org,
davem@davemloft.net
Subject: Re: [PATCH 1/7] driver-core : add class iteration api
Date: Sat, 12 Jan 2008 21:11:11 +0100 [thread overview]
Message-ID: <20080112201111.GA8129@ami.dom.local> (raw)
In-Reply-To: <20080112094754.GA2893@darkstar.te-china.tietoenator.com>
On Sat, Jan 12, 2008 at 05:47:54PM +0800, Dave Young wrote:
> Add the following class iteration functions for driver use:
> class_for_each_device
> class_find_device
> class_for_each_child
> class_find_child
>
> Signed-off-by: Dave Young <hidave.darkstar@gmail.com>
>
> ---
> drivers/base/class.c | 159 +++++++++++++++++++++++++++++++++++++++++++++++++
> include/linux/device.h | 8 ++
> 2 files changed, 167 insertions(+)
>
> diff -upr linux/drivers/base/class.c linux.new/drivers/base/class.c
> --- linux/drivers/base/class.c 2008-01-12 14:42:24.000000000 +0800
> +++ linux.new/drivers/base/class.c 2008-01-12 14:42:24.000000000 +0800
> @@ -798,6 +798,165 @@ void class_device_put(struct class_devic
> kobject_put(&class_dev->kobj);
> }
>
> +/**
> + * class_for_each_device - device iterator
> + * @class: the class we're iterating
> + * @data: data for the callback
> + * @fn: function to be called for each device
> + *
> + * Iterate over @class's list of devices, and call @fn for each,
> + * passing it @data.
> + *
> + * We check the return of @fn each time. If it returns anything
> + * other than 0, we break out and return that value.
> + */
> +int class_for_each_device(struct class *class, void *data,
> + int (*fn)(struct device *, void *))
> +{
> + struct device *dev;
> + int error = 0;
> +
> + if (!class)
> + return -EINVAL;
> + down(&class->sem);
> + list_for_each_entry(dev, &class->devices, node) {
Probably some tiny oversight, but I see this comment to struct class
doesn't mention devices list, so maybe this needs to be updated BTW?:
(from include/linux/device.h)
" struct semaphore sem; /* locks both the children and interfaces lists */"
Regards,
Jarek P.
next prev parent reply other threads:[~2008-01-12 20:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 9:47 [PATCH 1/7] driver-core : add class iteration api Dave Young
2008-01-12 10:50 ` Stefan Richter
2008-01-14 1:32 ` Dave Young
2008-01-12 20:11 ` Jarek Poplawski [this message]
2008-01-14 1:36 ` Dave Young
2008-01-14 6:58 ` Jarek Poplawski
2008-01-14 7:00 ` Dave Young
2008-01-14 12:13 ` Cornelia Huck
2008-01-15 0:17 ` Dave Young
2008-01-15 9:13 ` Dave Young
2008-01-15 9:45 ` Cornelia Huck
2008-01-22 5:54 ` [PATCH 1/6] " Dave Young
2008-01-22 6:06 ` Dave Young
2008-01-22 6:24 ` David Brownell
2008-01-22 6:30 ` Dave Young
2008-01-22 7:27 ` Dave Young
2008-01-22 8:44 ` Cornelia Huck
2008-01-22 22:25 ` Greg KH
2008-01-23 1:02 ` Dave Young
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=20080112201111.GA8129@ami.dom.local \
--to=jarkao2@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=a.zummo@towertech.it \
--cc=cbou@mail.ru \
--cc=davem@davemloft.net \
--cc=david-b@pacbell.net \
--cc=dwmw2@infradead.org \
--cc=gregkh@suse.de \
--cc=hidave.darkstar@gmail.com \
--cc=krh@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=stefanr@s5r6.in-berlin.de \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.