Re: [PATCH 12/15] driver core: Implement tagged directory support for device classes.
From: Eric W. Biederman <hidden>
Date: 2008-07-14 02:02:28
6 messages, 3 authors, 2008-07-19 · open the first message on its own page
From: Eric W. Biederman <hidden>
Date: 2008-07-14 02:02:28
Greg KH [off-list ref] writes:
Sorry, Greg is walking out the door in 30 minutes for a much needed week long vacation and can't look into this right now :( I'll be able to review it next weekend, sorry for the delay.
Any progress in reviewing these changes, and seeing if you can stand to merge them? Eric
From: Tejun Heo <hidden>
Date: 2008-07-16 03:25:50
Eric W. Biederman wrote:
Greg KH [off-list ref] writes:quoted
Sorry, Greg is walking out the door in 30 minutes for a much needed week long vacation and can't look into this right now :( I'll be able to review it next weekend, sorry for the delay.Any progress in reviewing these changes, and seeing if you can stand to merge them?
Greg, please disregard my earlier NACKs and commit the patches if you're okay with them. I'm working on cleaning it up but I don't think I'll be able to make it in time for merge window and as Eric said getting the functionality in place is more important at this point as it doesn't affect user visible interface. Eric, with the multiple superblocks, sysfs now uses inode from the default sysfs_sb with dentries from other sb's. Is this okay? Are there any other filesystems which do this? Thanks. -- tejun
From: Greg KH <gregkh@suse.de>
Date: 2008-07-17 23:13:56
On Wed, Jul 16, 2008 at 12:25:24PM +0900, Tejun Heo wrote:
Eric W. Biederman wrote:quoted
Greg KH [off-list ref] writes:quoted
Sorry, Greg is walking out the door in 30 minutes for a much needed week long vacation and can't look into this right now :( I'll be able to review it next weekend, sorry for the delay.Any progress in reviewing these changes, and seeing if you can stand to merge them?Greg, please disregard my earlier NACKs and commit the patches if you're okay with them. I'm working on cleaning it up but I don't think I'll be able to make it in time for merge window and as Eric said getting the functionality in place is more important at this point as it doesn't affect user visible interface.
Ok, I'll work to get these in where applicable. thanks, greg k-h
From: Tejun Heo <hidden>
Date: 2008-07-18 12:41:51
Greg KH wrote:
Ok, I'll work to get these in where applicable.
Did this get into 2.6.27? Or will this have to wait till .28? Thanks. -- tejun
From: Greg KH <gregkh@suse.de>
Date: 2008-07-18 18:57:05
On Fri, Jul 18, 2008 at 09:41:29PM +0900, Tejun Heo wrote:
Greg KH wrote:quoted
Ok, I'll work to get these in where applicable.Did this get into 2.6.27? Or will this have to wait till .28?
I haven't sent any patches to Linus yet for 2.6.27, so it hasn't gotten there yet. And due to the intrusiveness, and the fact that this hasn't been tested at all in any build tree yet, I can't in good concious submit this for .27 either. Part of this is my fault, I know, due to vacation and work, but also lots is due to the fact that the code showed up so late in the development cycle. I'll add it to my tree, and get it some testing in the next cycle of linux-next until 2.6.27 is out, and then if it's still looking good, go into .28. Hope this helps, greg k-h
From: Tejun Heo <hidden>
Date: 2008-07-19 01:08:21
Hello, Greg. Greg KH wrote:
On Fri, Jul 18, 2008 at 09:41:29PM +0900, Tejun Heo wrote:quoted
Greg KH wrote:quoted
Ok, I'll work to get these in where applicable.Did this get into 2.6.27? Or will this have to wait till .28?I haven't sent any patches to Linus yet for 2.6.27, so it hasn't gotten there yet. And due to the intrusiveness, and the fact that this hasn't been tested at all in any build tree yet, I can't in good concious submit this for .27 either. Part of this is my fault, I know, due to vacation and work, but also lots is due to the fact that the code showed up so late in the development cycle.
Heh... A lot of it is my fault too. Probably my share is bigger than anyone else's. Sorry Eric.
I'll add it to my tree, and get it some testing in the next cycle of linux-next until 2.6.27 is out, and then if it's still looking good, go into .28.
I was just curious how the merge will turn out as I'm about to do a refresh pass on the sysfs locking and stuff. I'm not sure yet whether to put those changes on top of or below ns patches but if I'll always keep the ns patches updated. Thank you. -- tejun