From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm@xmission.com (Eric W. Biederman) Subject: Re: [PATCH 0/13] sysfs lazification. Date: Tue, 17 Nov 2009 07:56:03 -0800 Message-ID: References: <20091106224857.GB32205@kroah.com> <20091117154116.GA22756@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Kay Sievers , linux-kernel@vger.kernel.org, Tejun Heo , Cornelia Huck , linux-fsdevel@vger.kernel.org, Eric Dumazet , Benjamin LaHaise To: Greg KH Return-path: In-Reply-To: <20091117154116.GA22756@kroah.com> (Greg KH's message of "Tue\, 17 Nov 2009 07\:41\:16 -0800") Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Greg KH writes: > On Tue, Nov 17, 2009 at 01:11:22AM -0800, Eric W. Biederman wrote: >> Greg KH writes: >> >> > On Tue, Nov 03, 2009 at 03:53:56AM -0800, Eric W. Biederman wrote: >> >> >> >> The sysfs code updates the vfs caches immediately when the sysfs data >> >> structures change causing a lot of unnecessary complications. The >> >> following patchset untangles that beast. Allowing for simpler >> >> more straight forward code, the removal of a hack from the vfs >> >> to support sysfs, and human comprehensible locking on sysfs. >> >> >> >> Most of these patches have already been reviewed and acked from the >> >> last time I had time to work on sysfs. >> >> >> >> In net the patches look like: >> > >> > Can you resend these based on the review that you just got, with the new >> > acks and changes so that I can apply them? >> >> Are you going to apply them soon? If you don't have time I can start >> a sysfs tree and just ask Linus to pull them. > > Well, as the merge window is not open right now, that might be tough to > get Linus to take them at the moment :) True. ;) > I was away last week, and will apply them to my tree this week, thanks > for your patience. I'm working on it. Eric