From: Yue Hu <zbestahu@gmail.com>
To: Thomas =?GB18030?B?V2VpgTCJOHNjaHVo?= <linux@weissschuh.net>
Cc: Gao Xiang <xiang@kernel.org>, Chao Yu <chao@kernel.org>,
Jeffle Xu <jefflexu@linux.alibaba.com>,
linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org,
huyue2@coolpad.com, zhangwen@coolpad.com
Subject: Re: [PATCH] erofs: make kobj_type structures constant
Date: Thu, 9 Feb 2023 13:54:28 +0800 [thread overview]
Message-ID: <20230209135428.00003233.zbestahu@gmail.com> (raw)
In-Reply-To: <20230209-kobj_type-erofs-v1-1-078c945e2c4b@weissschuh.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=GB18030, Size: 1545 bytes --]
On Thu, 09 Feb 2023 03:21:13 +0000
Thomas Wei08schuh <linux@weissschuh.net> wrote:
> Since commit ee6d3dd4ed48 ("driver core: make kobj_type constant.")
> the driver core allows the usage of const struct kobj_type.
>
> Take advantage of this to constify the structure definitions to prevent
> modification at runtime.
>
> Signed-off-by: Thomas Wei08schuh <linux@weissschuh.net>
Reviewed-by: Yue Hu <huyue2@coolpad.com>
> ---
> fs/erofs/sysfs.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/erofs/sysfs.c b/fs/erofs/sysfs.c
> index fd476961f742..435e515c0792 100644
> --- a/fs/erofs/sysfs.c
> +++ b/fs/erofs/sysfs.c
> @@ -179,13 +179,13 @@ static const struct sysfs_ops erofs_attr_ops = {
> .store = erofs_attr_store,
> };
>
> -static struct kobj_type erofs_sb_ktype = {
> +static const struct kobj_type erofs_sb_ktype = {
> .default_groups = erofs_groups,
> .sysfs_ops = &erofs_attr_ops,
> .release = erofs_sb_release,
> };
>
> -static struct kobj_type erofs_ktype = {
> +static const struct kobj_type erofs_ktype = {
> .sysfs_ops = &erofs_attr_ops,
> };
>
> @@ -193,7 +193,7 @@ static struct kset erofs_root = {
> .kobj = {.ktype = &erofs_ktype},
> };
>
> -static struct kobj_type erofs_feat_ktype = {
> +static const struct kobj_type erofs_feat_ktype = {
> .default_groups = erofs_feat_groups,
> .sysfs_ops = &erofs_attr_ops,
> };
>
> ---
> base-commit: 0983f6bf2bfc0789b51ddf7315f644ff4da50acb
> change-id: 20230209-kobj_type-erofs-0f0f4c901045
>
> Best regards,
next prev parent reply other threads:[~2023-02-09 5:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 3:21 [PATCH] erofs: make kobj_type structures constant Thomas Weißschuh
2023-02-09 3:22 ` Gao Xiang
2023-02-09 3:55 ` Jingbo Xu
2023-02-09 5:54 ` Yue Hu [this message]
2023-02-14 14:47 ` Chao Yu
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=20230209135428.00003233.zbestahu@gmail.com \
--to=zbestahu@gmail.com \
--cc=chao@kernel.org \
--cc=huyue2@coolpad.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=xiang@kernel.org \
--cc=zhangwen@coolpad.com \
/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