Re: [PATCH] fix valid but harmless sparse warning in xfs_log

xfs

Re: [PATCH] fix valid but harmless sparse warning in xfs_log_recovery.c

To:	Lachlan McIlroy <lachlan@xxxxxxx>
Subject:	Re: [PATCH] fix valid but harmless sparse warning in xfs_log_recovery.c
From:	Christoph Hellwig <hch@xxxxxx>
Date:	Tue, 18 Sep 2007 16:39:04 +0200
Cc:	Christoph Hellwig <hch@xxxxxx>, xfs@xxxxxxxxxxx
In-reply-to:	<46EF6A6A.3080702@sgi.com>
References:	<20070916120433.GA31602@lst.de> <46EF6A6A.3080702@sgi.com>
Sender:	xfs-bounce@xxxxxxxxxxx
User-agent:	Mutt/1.3.28i

On Tue, Sep 18, 2007 at 04:04:26PM +1000, Lachlan McIlroy wrote:
> Ah thanks for that, my goof.

Can you and Tim make sure this goes to Linus?  I saw Tim sent out
your original fix, and I really don't want to regress on sparse warnings
in mainline.

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[PATCH] fix valid but harmless sparse warning in xfs_log_recovery.c, Christoph Hellwig Message not available Re: [PATCH] fix valid but harmless sparse warning in xfs_log_recovery.c, Christoph Hellwig <=

Previous by Date:	Re: [PATCH 1/2] kill unnessecary ioops indirection, Christoph Hellwig
Next by Date:	Re: 2.6.20 (XFS? related) crash after uptime of > 180 days during apt-get dist-upgrade on Debian Testing, Justin Piszcz
Previous by Thread:	[PATCH] fix valid but harmless sparse warning in xfs_log_recovery.c, Christoph Hellwig
Next by Thread:	[PATCH] fix 32-bit compat ioctls for GETXFLAGS, SETXFLAGS, GETVERSION, Eric Sandeen
Indexes:	[Date] [Thread] [Top] [All Lists]