From: Aniroop Mathur <aniroop.mathur@gmail.com>
To: linux-kernel@vger.kernel.org, linux-hotplug@vger.kernel.org,
gregkh@linuxfoundation.org
Subject: [Question: Drivers/base/core.c] Why dev->init_name = NULL in device_add function ?
Date: Fri, 01 Aug 2014 17:25:23 +0000 [thread overview]
Message-ID: <CADYu30_FciG_aTTV4DFNdy+CdRChMYQ7pAGZGambE1F9s=ofYQ@mail.gmail.com> (raw)
Dear Mr. Greg Kroah-Hartman and Linux Community,
Greetings of the day !! :)
I am Aniroop Mathur working on Linux Kernel for last two years.
I am stuck at one point and could not find the solution over internet.
I posted on linuxquestions.org too.
So I need your help and suggestion for it.
Can you please help in answering my query as below:
==========================In function device_add of /drivers/base/core.c file, it is mentioned:
/*
* for statically allocated devices, which should all be converted
* some day, we need to initialize the name. We prevent reading back
* the name, and force the use of dev_name()
*/
if (dev->init_name) {
dev_set_name(dev, "%s", dev->init_name);
dev->init_name = NULL;
}
Except forcing the use of dev_name to read device name,
Is there any other reason to make init_name as NULL ?
And if it is not made NULL, is there any problem or side-effect ?
===========================
Link at linuxquestions.org:
http://www.linuxquestions.org/questions/linux-kernel-70/why-dev-init_name-%3D-null-in-device_add-function-4175504749/
Thanks a lot in advance !
Best Regards,
Aniroop Mathur
next reply other threads:[~2014-08-01 17:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 17:25 Aniroop Mathur [this message]
2014-08-01 19:23 ` [Question: Drivers/base/core.c] Why dev->init_name = NULL in device_add function ? Greg KH
2014-08-01 22:36 ` Aniroop Mathur
2014-08-01 22:41 ` Greg KH
2014-08-01 23:56 ` Aniroop Mathur
2014-08-02 2:39 ` Greg KH
2014-08-03 18:54 ` Aniroop Mathur
2014-08-04 4:35 ` Greg KH
2014-08-04 17:11 ` Aniroop Mathur
2014-08-03 16:25 ` Aniroop Mathur
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='CADYu30_FciG_aTTV4DFNdy+CdRChMYQ7pAGZGambE1F9s=ofYQ@mail.gmail.com' \
--to=aniroop.mathur@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).