| To: | Christoph Hellwig <hch@xxxxxx> |
|---|---|
| Subject: | sparse (was Re: [PATCH] xfs: fix brown paperbag quota-aware stafs bug) |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Thu, 13 Jul 2006 13:49:27 +1000 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20060711102341.C1702118@xxxxxxxxxxxxxxxxxxxxxxxx>; from nathans@xxxxxxx on Tue, Jul 11, 2006 at 10:23:42AM +1000 |
| References: | <20060710165539.GA26673@xxxxxx> <20060711102341.C1702118@xxxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Tue, Jul 11, 2006 at 10:23:42AM +1000, Nathan Scott wrote: > On Mon, Jul 10, 2006 at 06:55:39PM +0200, Christoph Hellwig wrote: > ... > > (I wish someone at SGI would run sparse once in a while..) > > Indeed, my bad. I'm much more motivated to do so now, thanks. :) Do you see this kind of warning from sparse, for debug builds? CHECK fs/xfs/xfs_ialloc_btree.c fs/xfs/xfs_alloc_btree.c:922:4: error: too long token expansion Looks like an assert (guess it expands to a fairly long string, after cpp-style expansion) - is there any way to make sparse not warn/error on these? thanks. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] xfs: remove unused locking flags, Christoph Hellwig |
|---|---|
| Next by Date: | Re: sparse (was Re: [PATCH] xfs: fix brown paperbag quota-aware stafs bug), Christoph Hellwig |
| Previous by Thread: | Re: [PATCH] xfs: fix brown paperbag quota-aware stafs bug, Nathan Scott |
| Next by Thread: | Re: sparse (was Re: [PATCH] xfs: fix brown paperbag quota-aware stafs bug), Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |