From: Greg KH <greg@kroah.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [4/12] SYSFS: Add sysfs_add/remove_files utility functions
Date: Tue, 5 Jan 2010 15:20:18 -0800 [thread overview]
Message-ID: <20100105232018.GA815@kroah.com> (raw)
In-Reply-To: <20100105162106.GE1778@basil.fritz.box>
On Tue, Jan 05, 2010 at 05:21:06PM +0100, Andi Kleen wrote:
> On Tue, Jan 05, 2010 at 06:53:09AM -0800, Greg KH wrote:
> > On Tue, Jan 05, 2010 at 12:48:01PM +0100, Andi Kleen wrote:
> > >
> > > Adding/Removing a whole array of attributes is very common. Add a standard
> > > utility function to do this with a simple function call, instead of
> > > requiring drivers to open code this.
> >
> > Hm, that is what the sysfs_create_group(), sysfs_update_group(), and
> > sysfs_remove_group() functions are for. We don't need to add any new
> > functions that do the same thing, right?
>
> Hmm, originally I didn't use them because they created a sub-directory,
> but I see now that's optional.
>
> Still the input format is completely different and doesn't fit into
> the ->attrs list that are used elsewhere (e.g. for the sysdev_classes)
> So using groups would need a lot of restructuring.
Argh, you are right.
Damm I hate the sysdev code, I need to dig up my "make drivers bind to
multiple devices" tree and get it up to date so we can just delete the
things completly and move to a "real" struct device instead.
> Also similar code as I have is already in a lot of places, which
> over time will be converted. So it's definitely less code than
> before.
Ok, good point, I'll queue this up, and hopefully be able to delete it
all in 6-8 months again :)
thanks,
greg k-h
next prev parent reply other threads:[~2010-01-05 23:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 11:47 [PATCH] [0/12] SYSFS: Sysfs attribute improvements Andi Kleen
2010-01-05 11:47 ` [PATCH] [1/12] SYSFS: Pass attribute in sysdev_class attributes show/store Andi Kleen
2010-01-05 14:53 ` Greg KH
2010-01-05 11:47 ` [PATCH] [2/12] SYSFS: Convert node driver class attributes to be data driven Andi Kleen
2010-01-05 11:48 ` [PATCH] [3/12] SYSDEV: Convert cpu driver sysdev class attributes Andi Kleen
2010-01-05 11:48 ` [PATCH] [4/12] SYSFS: Add sysfs_add/remove_files utility functions Andi Kleen
2010-01-05 14:53 ` Greg KH
2010-01-05 16:21 ` Andi Kleen
2010-01-05 23:20 ` Greg KH [this message]
2010-01-05 11:48 ` [PATCH] [5/12] SYSFS: Add attribute array to sysdev classes Andi Kleen
2010-01-05 14:54 ` Greg KH
2010-01-05 16:24 ` Andi Kleen
2010-01-05 23:20 ` Greg KH
2010-01-05 11:48 ` [PATCH] [6/12] SYSDEV: Convert node driver Andi Kleen
2010-01-05 11:48 ` [PATCH] [7/12] SYSDEV: Use sysdev_class attribute arrays in " Andi Kleen
2010-01-05 11:48 ` [PATCH] [8/12] SYSFS: Add sysdev_create/remove_files Andi Kleen
2010-01-05 11:48 ` [PATCH] [9/12] SYSFS: Fix type of sysdev class attribute in memory driver Andi Kleen
2010-01-05 11:48 ` [PATCH] [10/12] SYSDEV: Add attribute argument to class_attribute show/store Andi Kleen
2010-01-05 11:48 ` [PATCH] [11/12] SYSFS: Add class_attr_string for simple read-only string Andi Kleen
2010-01-05 11:48 ` [PATCH] [12/12] SYSFS: Convert some drivers to CLASS_ATTR_STRING Andi Kleen
2010-01-05 14:55 ` [PATCH] [0/12] SYSFS: Sysfs attribute improvements 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=20100105232018.GA815@kroah.com \
--to=greg@kroah.com \
--cc=andi@firstfloor.org \
--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