From: "Darrick J. Wong" <djwong@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: sysfs: use default_groups in kobj_type
Date: Mon, 3 Jan 2022 11:13:21 -0800 [thread overview]
Message-ID: <20220103191321.GA31583@magnolia> (raw)
In-Reply-To: <20211228144641.392347-1-gregkh@linuxfoundation.org>
On Tue, Dec 28, 2021 at 03:46:41PM +0100, Greg Kroah-Hartman wrote:
> There are currently 2 ways to create a set of sysfs files for a
> kobj_type, through the default_attrs field, and the default_groups
> field. Move the xfs sysfs code to use default_groups field which has
> been the preferred way since aa30f47cf666 ("kobject: Add support for
> default attribute groups to kobj_type") so that we can soon get rid of
> the obsolete default_attrs field.
>
> Cc: "Darrick J. Wong" <djwong@kernel.org>
> Cc: linux-xfs@vger.kernel.org
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Looks good to me. Shall I take this through the xfs tree?
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> fs/xfs/xfs_error.c | 3 ++-
> fs/xfs/xfs_sysfs.c | 16 ++++++++++------
> 2 files changed, 12 insertions(+), 7 deletions(-)
>
> diff --git a/fs/xfs/xfs_error.c b/fs/xfs/xfs_error.c
> index 81c445e9489b..749fd18c4f32 100644
> --- a/fs/xfs/xfs_error.c
> +++ b/fs/xfs/xfs_error.c
> @@ -213,11 +213,12 @@ static struct attribute *xfs_errortag_attrs[] = {
> XFS_ERRORTAG_ATTR_LIST(ag_resv_fail),
> NULL,
> };
> +ATTRIBUTE_GROUPS(xfs_errortag);
>
> static struct kobj_type xfs_errortag_ktype = {
> .release = xfs_sysfs_release,
> .sysfs_ops = &xfs_errortag_sysfs_ops,
> - .default_attrs = xfs_errortag_attrs,
> + .default_groups = xfs_errortag_groups,
> };
>
> int
> diff --git a/fs/xfs/xfs_sysfs.c b/fs/xfs/xfs_sysfs.c
> index 8608f804388f..574b80c29fe1 100644
> --- a/fs/xfs/xfs_sysfs.c
> +++ b/fs/xfs/xfs_sysfs.c
> @@ -67,11 +67,12 @@ static const struct sysfs_ops xfs_sysfs_ops = {
> static struct attribute *xfs_mp_attrs[] = {
> NULL,
> };
> +ATTRIBUTE_GROUPS(xfs_mp);
>
> struct kobj_type xfs_mp_ktype = {
> .release = xfs_sysfs_release,
> .sysfs_ops = &xfs_sysfs_ops,
> - .default_attrs = xfs_mp_attrs,
> + .default_groups = xfs_mp_groups,
> };
>
> #ifdef DEBUG
> @@ -239,11 +240,12 @@ static struct attribute *xfs_dbg_attrs[] = {
> #endif
> NULL,
> };
> +ATTRIBUTE_GROUPS(xfs_dbg);
>
> struct kobj_type xfs_dbg_ktype = {
> .release = xfs_sysfs_release,
> .sysfs_ops = &xfs_sysfs_ops,
> - .default_attrs = xfs_dbg_attrs,
> + .default_groups = xfs_dbg_groups,
> };
>
> #endif /* DEBUG */
> @@ -296,11 +298,12 @@ static struct attribute *xfs_stats_attrs[] = {
> ATTR_LIST(stats_clear),
> NULL,
> };
> +ATTRIBUTE_GROUPS(xfs_stats);
>
> struct kobj_type xfs_stats_ktype = {
> .release = xfs_sysfs_release,
> .sysfs_ops = &xfs_sysfs_ops,
> - .default_attrs = xfs_stats_attrs,
> + .default_groups = xfs_stats_groups,
> };
>
> /* xlog */
> @@ -381,11 +384,12 @@ static struct attribute *xfs_log_attrs[] = {
> ATTR_LIST(write_grant_head),
> NULL,
> };
> +ATTRIBUTE_GROUPS(xfs_log);
>
> struct kobj_type xfs_log_ktype = {
> .release = xfs_sysfs_release,
> .sysfs_ops = &xfs_sysfs_ops,
> - .default_attrs = xfs_log_attrs,
> + .default_groups = xfs_log_groups,
> };
>
> /*
> @@ -534,12 +538,12 @@ static struct attribute *xfs_error_attrs[] = {
> ATTR_LIST(retry_timeout_seconds),
> NULL,
> };
> -
> +ATTRIBUTE_GROUPS(xfs_error);
>
> static struct kobj_type xfs_error_cfg_ktype = {
> .release = xfs_sysfs_release,
> .sysfs_ops = &xfs_sysfs_ops,
> - .default_attrs = xfs_error_attrs,
> + .default_groups = xfs_error_groups,
> };
>
> static struct kobj_type xfs_error_ktype = {
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-01-03 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 14:46 [PATCH] xfs: sysfs: use default_groups in kobj_type Greg Kroah-Hartman
2022-01-03 19:13 ` Darrick J. Wong [this message]
2022-01-04 7:01 ` Greg Kroah-Hartman
2022-01-04 18:05 ` Darrick J. Wong
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=20220103191321.GA31583@magnolia \
--to=djwong@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@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