From: Corey Minyard <minyard@acm.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
Ivan Orlov <ivan.orlov0322@gmail.com>,
openipmi-developer@lists.sourceforge.net
Subject: Re: [PATCH] ipmi: make ipmi_class a static const structure
Date: Tue, 20 Jun 2023 10:06:05 -0500 [thread overview]
Message-ID: <ZJHAXakwV6slpZB/@mail.minyard.net> (raw)
In-Reply-To: <20230620143701.577657-2-gregkh@linuxfoundation.org>
On Tue, Jun 20, 2023 at 04:37:02PM +0200, Greg Kroah-Hartman wrote:
> From: Ivan Orlov <ivan.orlov0322@gmail.com>
>
> Now that the driver core allows for struct class to be in read-only
> memory, move the ipmi_class structure to be declared at build time
> placing it into read-only memory, instead of having to be dynamically
> allocated at boot time.
This is in my next tree and seems to work fine. Thanks.
-corey
>
> Cc: Corey Minyard <minyard@acm.org>
> Cc: openipmi-developer@lists.sourceforge.net
> Suggested-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Ivan Orlov <ivan.orlov0322@gmail.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
> drivers/char/ipmi/ipmi_devintf.c | 24 ++++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/char/ipmi/ipmi_devintf.c b/drivers/char/ipmi/ipmi_devintf.c
> index 73e5a9e28f85..332082e02ea5 100644
> --- a/drivers/char/ipmi/ipmi_devintf.c
> +++ b/drivers/char/ipmi/ipmi_devintf.c
> @@ -807,7 +807,9 @@ struct ipmi_reg_list {
> static LIST_HEAD(reg_list);
> static DEFINE_MUTEX(reg_list_mutex);
>
> -static struct class *ipmi_class;
> +static const struct class ipmi_class = {
> + .name = "ipmi",
> +};
>
> static void ipmi_new_smi(int if_num, struct device *device)
> {
> @@ -822,7 +824,7 @@ static void ipmi_new_smi(int if_num, struct device *device)
> entry->dev = dev;
>
> mutex_lock(®_list_mutex);
> - device_create(ipmi_class, device, dev, NULL, "ipmi%d", if_num);
> + device_create(&ipmi_class, device, dev, NULL, "ipmi%d", if_num);
> list_add(&entry->link, ®_list);
> mutex_unlock(®_list_mutex);
> }
> @@ -840,7 +842,7 @@ static void ipmi_smi_gone(int if_num)
> break;
> }
> }
> - device_destroy(ipmi_class, dev);
> + device_destroy(&ipmi_class, dev);
> mutex_unlock(®_list_mutex);
> }
>
> @@ -860,15 +862,13 @@ static int __init init_ipmi_devintf(void)
>
> pr_info("ipmi device interface\n");
>
> - ipmi_class = class_create("ipmi");
> - if (IS_ERR(ipmi_class)) {
> - pr_err("ipmi: can't register device class\n");
> - return PTR_ERR(ipmi_class);
> - }
> + rv = class_register(&ipmi_class);
> + if (rv)
> + return rv;
>
> rv = register_chrdev(ipmi_major, DEVICE_NAME, &ipmi_fops);
> if (rv < 0) {
> - class_destroy(ipmi_class);
> + class_unregister(&ipmi_class);
> pr_err("ipmi: can't get major %d\n", ipmi_major);
> return rv;
> }
> @@ -880,7 +880,7 @@ static int __init init_ipmi_devintf(void)
> rv = ipmi_smi_watcher_register(&smi_watcher);
> if (rv) {
> unregister_chrdev(ipmi_major, DEVICE_NAME);
> - class_destroy(ipmi_class);
> + class_unregister(&ipmi_class);
> pr_warn("ipmi: can't register smi watcher\n");
> return rv;
> }
> @@ -895,11 +895,11 @@ static void __exit cleanup_ipmi(void)
> mutex_lock(®_list_mutex);
> list_for_each_entry_safe(entry, entry2, ®_list, link) {
> list_del(&entry->link);
> - device_destroy(ipmi_class, entry->dev);
> + device_destroy(&ipmi_class, entry->dev);
> kfree(entry);
> }
> mutex_unlock(®_list_mutex);
> - class_destroy(ipmi_class);
> + class_unregister(&ipmi_class);
> ipmi_smi_watcher_unregister(&smi_watcher);
> unregister_chrdev(ipmi_major, DEVICE_NAME);
> }
> --
> 2.41.0
>
prev parent reply other threads:[~2023-06-20 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 14:37 Greg Kroah-Hartman
2023-06-20 15:06 ` Corey Minyard [this message]
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=ZJHAXakwV6slpZB/@mail.minyard.net \
--to=minyard@acm.org \
--cc=gregkh@linuxfoundation.org \
--cc=ivan.orlov0322@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome