Hello, all.
There are four patchsets going out today, which are...
PS-1 misc updates
PS-2 allow suicide
PS-3 divorce sysfs from kobject and driver model
PS-4 implement new features - symlink name formatting, plugging, batch
error handling
And this is PS-1. This patchset is on top of
drivers/sysfs-rewrite-sysfs_move_dir-in-terms-of-sysfs-dirents.patch
in gregkh-2.6 as of today (20070920, based on 2.6.23-rc6-git4) and
contains the following 15 patches.
0001-sysfs-kill-SYSFS_FLAG_REMOVED.patch
0002-sysfs-fix-comments-of-sysfs_add-remove_one.patch
0003-sysfs-fix-sysfs_chmod_file-such-that-it-updates-s.patch
0004-sysfs-clean-up-header-files.patch
0005-sysfs-kill-sysfs_update_file.patch
0006-sysfs-reposition-sysfs_dirent-s_mode.patch
0007-sysfs-kill-unnecessary-sysfs_get-in-open-paths.patch
0008-sysfs-kill-unnecessary-NULL-pointer-check-in-sysfs_.patch
0009-sysfs-make-bin-attr-open-get-active-reference-of-pa.patch
0010-sysfs-make-s_elem-an-anonymous-union.patch
0011-sysfs-open-code-sysfs_attach_dentry.patch
0012-sysfs-make-sysfs_root-a-regular-directory-dirent.patch
0013-sysfs-move-sysfs_dirent-s_children-into-sysfs_dire.patch
0014-sysfs-implement-sysfs_open_dirent.patch
0015-sysfs-move-sysfs-file-poll-implementation-to-sysfs_.patch
0001 reverses earlier driver/sysfs-kill-sysfs_flag_removed.patch and
as such both patches can just be dropped.
0002-0003 contains misc fixes. 0004 reorganizes and cleans up sysfs
header files. As these four patchsets are gonna disrupt out-of-tree
changes anyway, this is a good time to clean up. 0005-0013 are also
clean up patches. They change and tune things here and there but
don't really cause behavior changes.
0014-0015 implements sysfs_open_dirent and moves poll implementation
to it. This reduces the size of sysfs_dirent and fixes dangling
sleeper bug in the current poll implementation.
Thanks.
--
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
