From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: device_register and device_create_file rules
Date: Fri, 26 Jul 2013 12:29:37 -0700 [thread overview]
Message-ID: <51F2CE21.8030000@linux.intel.com> (raw)
I am aware that it it is always recommended that attributes must be
associate via attribute groups when calling device_register() .
This way when the device is created, user space can always see
attributes once they get device create notification via uevent.
I have need to create/delete attributes on fly using
device_create_file/device_remove_file. In past several drivers did that.
But with the enforcements of device model for new class of drivers, is
it a big NO? I am not aware of change notification calls other than for
kobject_uevent.
Thanks,
Srinivas
reply other threads:[~2013-07-26 19:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51F2CE21.8030000@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.