From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 5/7] samples/kobject: add is_visible() callback to attribute group
Date: Tue, 19 Aug 2025 13:24:04 +0200 [thread overview]
Message-ID: <2025081931-deprive-overtime-b353@gregkh> (raw)
In-Reply-To: <20250811-sysfs-const-attr-prep-v3-5-0d973ff46afc@weissschuh.net>
On Mon, Aug 11, 2025 at 11:14:31AM +0200, Thomas Weißschuh wrote:
> There was no example for the is_visible() callback so far.
>
> It will also become an example and test for the constification of
> 'struct attribute' later.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> samples/kobject/kset-example.c | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/samples/kobject/kset-example.c b/samples/kobject/kset-example.c
> index 579ce150217c6e613887e32a08206573543b3091..1aac595ed9498b30448485a60d9376cb5b5ea1d3 100644
> --- a/samples/kobject/kset-example.c
> +++ b/samples/kobject/kset-example.c
> @@ -178,7 +178,22 @@ static struct attribute *foo_default_attrs[] = {
> &bar_attribute.attr,
> NULL, /* need to NULL terminate the list of attributes */
> };
> -ATTRIBUTE_GROUPS(foo_default);
> +
> +static umode_t foo_default_attrs_is_visible(struct kobject *kobj,
> + struct attribute *attr,
> + int n)
> +{
> + /* Hide attributes with the same name as the kobject. */
> + if (strcmp(kobject_name(kobj), attr->name) == 0)
> + return 0;
> + return attr->mode;
> +}
> +
> +static const struct attribute_group foo_default_group = {
> + .attrs = foo_default_attrs,
> + .is_visible = foo_default_attrs_is_visible,
> +};
> +__ATTRIBUTE_GROUPS(foo_default);
Wait, why? Shouldn't ATTRIBUTE_GROUPS() still work here? No one should
have to call __ATTRIBUTE_GROUPS() in their code, that's just going to be
too messy over time.
thanks
greg k-h
next prev parent reply other threads:[~2025-08-19 11:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 9:14 [PATCH v3 0/7] sysfs: prepare the constification of struct attribute Thomas Weißschuh
2025-08-11 9:14 ` [PATCH v3 1/7] sysfs: attribute_group: allow registration of const attribute Thomas Weißschuh
2025-08-19 11:22 ` Greg Kroah-Hartman
2025-08-19 13:59 ` Thomas Weißschuh
2025-08-19 14:10 ` Greg Kroah-Hartman
2025-08-19 14:15 ` Thomas Weißschuh
2025-08-11 9:14 ` [PATCH v3 2/7] sysfs: transparently handle const pointers in ATTRIBUTE_GROUPS() Thomas Weißschuh
2025-08-11 9:14 ` [PATCH v3 3/7] sysfs: introduce __SYSFS_FUNCTION_ALTERNATIVE() Thomas Weißschuh
2025-08-11 9:14 ` [PATCH v3 4/7] sysfs: attribute_group: enable const variants of is_visible() Thomas Weißschuh
2025-08-19 11:28 ` Greg Kroah-Hartman
2025-08-19 14:07 ` Thomas Weißschuh
2025-08-11 9:14 ` [PATCH v3 5/7] samples/kobject: add is_visible() callback to attribute group Thomas Weißschuh
2025-08-19 11:24 ` Greg Kroah-Hartman [this message]
2025-08-19 14:00 ` Thomas Weißschuh
2025-08-11 9:14 ` [PATCH v3 6/7] samples/kobject: constify 'struct foo_attribute' Thomas Weißschuh
2025-08-19 11:27 ` Greg Kroah-Hartman
2025-08-11 9:14 ` [PATCH v3 7/7] sysfs: simplify attribute definition macros Thomas Weißschuh
2025-08-12 14:36 ` [PATCH v3 0/7] sysfs: prepare the constification of struct attribute 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=2025081931-deprive-overtime-b353@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dakr@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=rafael@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