On Fri, Jul 27, 2012 at 12:02:41PM +0800, Bryan Wu wrote: > Send a uevent notification whenever a new sysfs file is created to allow > userspace processes such as udev to modify permissions on the new files.
This makes no sense, why not just call kobject_uevent after creating the file when needed? Wrapping it up in a single function call doesn't add any benefit that I can see, can you? > > This new API function helps to do this. > > Signed-off-by: Bryan Wu <bryan...@canonical.com> > --- > fs/sysfs/file.c | 28 ++++++++++++++++++++++++++++ > include/linux/sysfs.h | 13 +++++++++++++ > 2 files changed, 41 insertions(+) > > diff --git a/fs/sysfs/file.c b/fs/sysfs/file.c > index 00012e3..5a22d13 100644 > --- a/fs/sysfs/file.c > +++ b/fs/sysfs/file.c > @@ -576,6 +576,34 @@ int sysfs_create_file(struct kobject * kobj, const > struct attribute * attr) > > } > > +/** > + * sysfs_create_file_uevent - create an attribute file for an object > + and send a uevent to userspace. kerneldoc needs to be on one line for function names, right? greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
