public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ivan Orlov <ivan.orlov0322@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: tomas.winkler@intel.com, arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mei: make mei_class a static const structure
Date: Fri, 11 Aug 2023 23:52:07 +0400	[thread overview]
Message-ID: <d3080712-d7ca-c227-df42-7b8da877d015@gmail.com> (raw)
In-Reply-To: <2023081112-wistful-coping-f775@gregkh>

On 8/11/23 23:40, Greg KH wrote:
> On Thu, Aug 10, 2023 at 11:46:52PM +0400, Ivan Orlov wrote:
>> Now that the driver core allows for struct class to be in read-only
>> memory, move the mei_class structure to be declared at build time
>> placing it into read-only memory, instead of having to be dynamically
>> allocated at boot time.
>>
>> Suggested-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> Signed-off-by: Ivan Orlov <ivan.orlov0322@gmail.com>
>> ---
>>   drivers/misc/mei/main.c | 19 ++++++++++---------
>>   1 file changed, 10 insertions(+), 9 deletions(-)
>>
>> diff --git a/drivers/misc/mei/main.c b/drivers/misc/mei/main.c
>> index 51876da3fd65..902789d3106b 100644
>> --- a/drivers/misc/mei/main.c
>> +++ b/drivers/misc/mei/main.c
>> @@ -27,7 +27,9 @@
>>   #include "mei_dev.h"
>>   #include "client.h"
>>   
>> -static struct class *mei_class;
>> +static const struct class mei_class = {
>> +	.name = "mei",
>> +};
>>   static dev_t mei_devt;
> 
> Extra line after the new structure?
> 
>>   #define MEI_MAX_DEVS  MINORMASK
>>   static DEFINE_MUTEX(mei_minor_lock);
>> @@ -1115,7 +1117,7 @@ void mei_set_devstate(struct mei_device *dev, enum mei_dev_state state)
>>   
>>   	dev->dev_state = state;
>>   
>> -	clsdev = class_find_device_by_devt(mei_class, dev->cdev.dev);
>> +	clsdev = class_find_device_by_devt(&mei_class, dev->cdev.dev);
>>   	if (clsdev) {
>>   		sysfs_notify(&clsdev->kobj, NULL, "dev_state");
>>   		put_device(clsdev);
>> @@ -1232,7 +1234,7 @@ int mei_register(struct mei_device *dev, struct device *parent)
>>   		goto err_dev_add;
>>   	}
>>   
>> -	clsdev = device_create_with_groups(mei_class, parent, devno,
>> +	clsdev = device_create_with_groups(&mei_class, parent, devno,
>>   					   dev, mei_groups,
>>   					   "mei%d", dev->minor);
>>   
>> @@ -1264,7 +1266,7 @@ void mei_deregister(struct mei_device *dev)
>>   
>>   	mei_dbgfs_deregister(dev);
>>   
>> -	device_destroy(mei_class, devno);
>> +	device_destroy(&mei_class, devno);
>>   
>>   	mei_minor_free(dev);
>>   }
>> @@ -1274,10 +1276,9 @@ static int __init mei_init(void)
>>   {
>>   	int ret;
>>   
>> -	mei_class = class_create("mei");
>> -	if (IS_ERR(mei_class)) {
>> +	ret = class_register(&mei_class);
>> +	if (ret) {
>>   		pr_err("couldn't create class\n");
> 
> This message doesn't make sense anymore.  No need for it either, just
> remove it and do a simple:
> 		return err;
> here instead.
> 
> thanks,
> 
> greg k-h


Hi Greg,

Thank you for the review, I'll make the suggested changes and send you 
the V2.

--
Kind regards,
Ivan Orlov

      reply	other threads:[~2023-08-11 19:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 19:46 [PATCH] mei: make mei_class a static const structure Ivan Orlov
2023-08-11 19:40 ` Greg KH
2023-08-11 19:52   ` Ivan Orlov [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=d3080712-d7ca-c227-df42-7b8da877d015@gmail.com \
    --to=ivan.orlov0322@gmail.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomas.winkler@intel.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