Date: Tue, 29 May 2007 08:58:50 -0700
From: Greg KH <gregkh@suse.de>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Tejun Heo <htejun@gmail.com>, dmitry.torokhov@gmail.com, oneukum@suse.de,
       rpurdie@rpsys.net, stern@rowland.harvard.edu, maneesh@in.ibm.com,
       linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET 2.6.22-rc2-mm1] sysfs: assorted fixes
Message-ID: <20070529155850.GB7068@suse.de>
References: <1180368625600-git-send-email-htejun@gmail.com> <20070529160243.7ea4023d@gondolin.boeblingen.de.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070529160243.7ea4023d@gondolin.boeblingen.de.ibm.com>
User-Agent: Mutt/1.5.15 (2007-04-06)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1304
Lines: 36

On Tue, May 29, 2007 at 04:02:43PM +0200, Cornelia Huck wrote:
> On Tue, 29 May 2007 01:10:25 +0900,
> Tejun Heo <htejun@gmail.com> wrote:
> 
> > Hello, all.
> > 
> > This patchset contains two cleanups and three fixes.
> > 
> > #01: make-sysfs_alloc_ino-static, cleanup
> > #02: fix-parent-refcounting, fix
> > #03: reorganize-sysfs_new_inode-and-sysfs_create, cleanup and prep for #04
> > #04: use-iget_locked-instead-of-new_inode, fix
> > #05: fix-root-sysfs_dirent-root-dentry-association, fix
> > 
> >  fs/sysfs/dir.c   |  143 +++++++++++++++++++++++--------------------------------
> >  fs/sysfs/inode.c |  114 ++++++++++++++++++++++++-------------------
> >  fs/sysfs/mount.c |   19 ++++---
> >  fs/sysfs/sysfs.h |    6 +-
> >  4 files changed, 137 insertions(+), 145 deletions(-)
> > 
> > Please apply.  Thanks.
> 
> I've tested this patchset a bit on s390 (device attach/detach and
> moving devices around) and didn't encounter problems. As far as I can
> see, this looks sane.

It boots on this laptop just fine too :)

Thanks for testing,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/