From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: fix xfs_debug warnings
Date: Mon, 4 Apr 2011 10:21:25 +1000 [thread overview]
Message-ID: <20110404002125.GM6957@dastard> (raw)
In-Reply-To: <20110403105823.GA3872@infradead.org>
On Sun, Apr 03, 2011 at 06:58:23AM -0400, Christoph Hellwig wrote:
> On Sun, Apr 03, 2011 at 10:16:48AM +1000, Dave Chinner wrote:
> > Looks good, though I don't get those warnings using gcc-4.4.4. I
> > guess it's gcc-4.6 issuing the warnings?
>
> Debian testing recently updated to gcc 4.5.2 from gcc 4.4.x, I think
> that's when I started to see them.
Ok, my build box is still running on squeeze which would explain the
difference. I'll look at upgrading it in the not-too-distant future.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-04-04 0:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 18:13 f Christoph Hellwig
2011-04-02 22:09 ` [PATCH] xfs: fix xfs_debug warnings Christoph Hellwig
2011-04-03 0:16 ` Dave Chinner
2011-04-03 10:58 ` Christoph Hellwig
2011-04-04 0:21 ` Dave Chinner [this message]
2011-04-04 18:13 ` Alex Elder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110404002125.GM6957@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.