From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: htejun@gmail.com, linux-kernel@vger.kernel.org,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH 2/2] sysfs: add devm_sysfs_create_group() and friends
Date: Tue, 18 Jul 2017 13:26:06 -0700 [thread overview]
Message-ID: <20170718202606.GA36888@dtor-ws> (raw)
In-Reply-To: <20170718200336.GC3694@kroah.com>
On Tue, Jul 18, 2017 at 10:03:36PM +0200, Greg Kroah-Hartman wrote:
> On Tue, Jul 18, 2017 at 12:30:58PM -0700, Dmitry Torokhov wrote:
> > --- a/include/linux/sysfs.h
> > +++ b/include/linux/sysfs.h
> > @@ -282,6 +282,16 @@ int __compat_only_sysfs_link_entry_to_kobj(struct kobject *kobj,
> > struct kobject *target_kobj,
> > const char *target_name);
> >
> > +struct device;
>
> Put this in device.h instead?
I think we normally keep devm* and non-managed APIs together, like both
regulator*() and devm_regulator*() are in include/linux/regulator/consumer.h,
gpiod*() and devm_gpiod*() are in include/gpio/linux/consumer.h,
clk*() and devm_clk() are in include/linux/clk.h, and so forth.
I think there is benefit of having these together as well.
>
> > +int __must_check devm_sysfs_create_group(struct device *dev,
> > + const struct attribute_group *grp);
> > +int __must_check devm_sysfs_create_groups(struct device *dev,
> > + const struct attribute_group **groups);
> > +void devm_sysfs_remove_group(struct device *dev,
> > + const struct attribute_group *grp);
> > +void devm_sysfs_remove_groups(struct device *dev,
> > + const struct attribute_group **groups);
>
> I have finally moved the driver core to only accept/need "groups" not a
> single "group", so we should only need devm_sysfs_create_groups and
> devm_sysfs_remove_groups, right?
This makes total sense for the driver core, but individual drivers
usually have a single group. Requiring all of them to have array of
groups just adds unneeded boilerplate that I was trying to cut down.
>
> And do we need/want the non-devm versions:
> device_create_groups()
> device_remove_groups()
> ?
We already have non-managed sysfs_create_groups() and
sysfs_remove_groups().
>
> And you can probably drop the 'sysfs' from the function name if you
> want.
I think there is benefit of having devm version having name matching the
non-managed one:
sysfs_create_groups() and devm_sysfs_create_groups().
I hope you will reconsider.
Thanks!
--
Dmitry
next prev parent reply other threads:[~2017-07-18 20:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 19:30 [PATCH 0/2] New bind/unbingd uevents Dmitry Torokhov
2017-07-18 19:30 ` [PATCH 1/2] driver core: emit uevents when device is bound to a driver Dmitry Torokhov
2017-07-18 19:30 ` [PATCH 2/2] sysfs: add devm_sysfs_create_group() and friends Dmitry Torokhov
2017-07-18 20:03 ` Greg Kroah-Hartman
2017-07-18 20:26 ` Dmitry Torokhov [this message]
2017-07-19 7:34 ` Greg Kroah-Hartman
2017-07-18 20:05 ` [PATCH 0/2] New bind/unbingd uevents Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2017-02-13 0:36 [PATCH 1/2] driver core: emit uevents when device is bound to a driver Dmitry Torokhov
2017-02-13 0:36 ` [PATCH 2/2] sysfs: add devm_sysfs_create_group() and friends Dmitry Torokhov
2017-03-27 17:53 ` Dmitry Torokhov
2017-03-27 19:35 ` Greg Kroah-Hartman
2017-06-07 17:04 ` Dmitry Torokhov
2017-06-17 19:27 ` Greg Kroah-Hartman
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=20170718202606.GA36888@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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.