From: cgxu519 <cgxu519@gmx.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: tomas.winkler@intel.com, arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mei: expand minor range when registering chrdev region
Date: Tue, 12 Feb 2019 22:55:03 +0800 [thread overview]
Message-ID: <03e93235-9fc8-dbc5-49e4-45be8e715398@gmx.com> (raw)
In-Reply-To: <20190212092902.GD27450@kroah.com>
On 2/12/19 5:29 PM, Greg KH wrote:
> On Tue, Feb 12, 2019 at 02:02:52PM +0800, Chengguang Xu wrote:
>> Actually, total amount of available minor number
>> for a single major is MINORMARK + 1. So expand
>> minor range when registering chrdev region.
>>
>> Signed-off-by: Chengguang Xu <cgxu519@gmx.com>
>> ---
>> drivers/misc/mei/main.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/misc/mei/main.c b/drivers/misc/mei/main.c
>> index 87281b3695e6..3df54f1e1a8b 100644
>> --- a/drivers/misc/mei/main.c
>> +++ b/drivers/misc/mei/main.c
>> @@ -869,7 +869,7 @@ static const struct file_operations mei_fops = {
>>
>> static struct class *mei_class;
>> static dev_t mei_devt;
>> -#define MEI_MAX_DEVS MINORMASK
>> +#define MEI_MAX_DEVS (MINORMASK + 1)
> Why is this needed? Have you really run out of that many minor nodes
> for this driver?
Not really, practically maybe we cannot reach to the limit.
I was just curious why only one minor number left there and assumed
that was from a mistake(since I've seen similar mistake in other driver).
However, if it explicitly sets to MINORMASK for some reasons, then it's
better to keep as is.
Thanks
next prev parent reply other threads:[~2019-02-12 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 6:02 Chengguang Xu
2019-02-12 9:29 ` Greg KH
2019-02-12 14:55 ` cgxu519 [this message]
2019-02-12 15:22 ` Winkler, Tomas
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=03e93235-9fc8-dbc5-49e4-45be8e715398@gmx.com \
--to=cgxu519@gmx.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
all inboxes | Powered by JetHome®