From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org, David Gibson <dwg@au1.ibm.com>,
linuxppc-dev@ozlabs.org, "Kyle A. Lucke" <klucke@us.ibm.com>,
paulus@samba.org
Subject: Re: [PATCH] Introduce driver_create/remove_dir
Date: Wed, 12 Dec 2007 23:10:22 -0800 [thread overview]
Message-ID: <20071213071022.GB13764@kroah.com> (raw)
In-Reply-To: <20071212105633.725496cb.sfr@canb.auug.org.au>
On Wed, Dec 12, 2007 at 10:56:33AM +1100, Stephen Rothwell wrote:
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> drivers/base/driver.c | 24 ++++++++++++++++++++++++
> drivers/net/iseries_veth.c | 15 +++++++--------
> include/linux/device.h | 3 +++
> 3 files changed, 34 insertions(+), 8 deletions(-)
>
> Greg, does this look like a reasonable solution to iseries_veth accessing
> the "private" kobject in struct device_driver? This version is against
> maimline, but the stuff you have in mm would just need to update
> driver_create_dir ...
Hm, we just want to be able to get to the kobject somehow here. Not
create a new api that doesn't match up. I'll think about it and figure
something that matches the other portions of the api.
> Also something along the lines of device_add_dir() might be good if you
> want to hide the kobject in struct device as well.
As devices _should_ always be dynamic, hopefully I'll not have to do
that. But knowing some of the platform devices, I'm afraid I'll have to
do that split :)
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: michael@ellerman.id.au, linuxppc-dev@ozlabs.org,
"Kyle A. Lucke" <klucke@us.ibm.com>,
paulus@samba.org, linux-kernel@vger.kernel.org,
David Gibson <dwg@au1.ibm.com>
Subject: Re: [PATCH] Introduce driver_create/remove_dir
Date: Wed, 12 Dec 2007 23:10:22 -0800 [thread overview]
Message-ID: <20071213071022.GB13764@kroah.com> (raw)
In-Reply-To: <20071212105633.725496cb.sfr@canb.auug.org.au>
On Wed, Dec 12, 2007 at 10:56:33AM +1100, Stephen Rothwell wrote:
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> drivers/base/driver.c | 24 ++++++++++++++++++++++++
> drivers/net/iseries_veth.c | 15 +++++++--------
> include/linux/device.h | 3 +++
> 3 files changed, 34 insertions(+), 8 deletions(-)
>
> Greg, does this look like a reasonable solution to iseries_veth accessing
> the "private" kobject in struct device_driver? This version is against
> maimline, but the stuff you have in mm would just need to update
> driver_create_dir ...
Hm, we just want to be able to get to the kobject somehow here. Not
create a new api that doesn't match up. I'll think about it and figure
something that matches the other portions of the api.
> Also something along the lines of device_add_dir() might be good if you
> want to hide the kobject in struct device as well.
As devices _should_ always be dynamic, hopefully I'll not have to do
that. But knowing some of the platform devices, I'm afraid I'll have to
do that split :)
thanks,
greg k-h
next prev parent reply other threads:[~2007-12-13 7:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 9:30 drivers/net/iseries_veth.c dubious sysfs usage Greg KH
2007-12-05 9:30 ` Greg KH
2007-12-05 11:10 ` Michael Ellerman
2007-12-05 11:10 ` Michael Ellerman
2007-12-05 21:41 ` Greg KH
2007-12-05 21:41 ` Greg KH
2007-12-06 3:48 ` Michael Ellerman
2007-12-06 3:48 ` Michael Ellerman
2007-12-11 23:56 ` [PATCH] Introduce driver_create/remove_dir Stephen Rothwell
2007-12-11 23:56 ` Stephen Rothwell
2007-12-12 0:40 ` Randy Dunlap
2007-12-12 0:40 ` Randy Dunlap
2007-12-12 2:36 ` Stephen Rothwell
2007-12-12 2:36 ` Stephen Rothwell
2007-12-13 7:10 ` Greg KH [this message]
2007-12-13 7:10 ` Greg KH
2007-12-13 7:08 ` drivers/net/iseries_veth.c dubious sysfs usage Greg KH
2007-12-13 7:08 ` Greg KH
2007-12-24 2:52 ` Stephen Rothwell
2007-12-24 2:52 ` Stephen Rothwell
2007-12-24 5:01 ` Greg KH
2007-12-24 5:01 ` Greg KH
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=20071213071022.GB13764@kroah.com \
--to=greg@kroah.com \
--cc=dwg@au1.ibm.com \
--cc=klucke@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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.