Greg KH <gregkh@suse.de> writes:Yes. Al found problems. Al reviewed sysfs with my patchset on top of it. Al's review found problems in sysfs with my patchset on top of it. If you look at what Al found the majority of those problems exist in sysfs without my patches. Does the following sound like a workable path going forward? - Not merge for 2.6.28 (we are to close to the merge window for everyone's comfort). - Fix the small issues specific to tagged directory support that showed up in Al's review (patches sent). - Keep the patches the entire time in a public tree that merges into linux-next so that people treat this code base seriously. - Resolve the sysfs/vfs lock ordering problem mess that makes locking in sysfs excruciatingly difficult. - Merge other patches to fix Als other issues with sysfs. - Merge to 2.6.29 or wherever we are. Eric --
| Parag Warudkar | BUG: soft lockup - CPU#1 stuck for 15s! [swapper:0] |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| David Miller | Re: [BUG] New Kernel Bugs |
