public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <aelder@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfsprogs: fix gcc 4.6 variable set but not used warnings
Date: Fri, 15 Jul 2011 16:39:21 -0500	[thread overview]
Message-ID: <1310765961.2921.98.camel@doink> (raw)
In-Reply-To: <20110630202505.GA23276@infradead.org>

On Thu, 2011-06-30 at 16:25 -0400, Christoph Hellwig wrote:
> Signed-off-by: Christoph Hellwig <hch@lst.de>

This one looks good to me too.  As with the previous
one I tried it out on x86_64, i386, and ia64 to
get better coverage.  I found a few more of this
type of warning, which I'll send to you as another
patch to combine with this one.

Or, if you prefer you can take my Reviewed-by
on this and I'll do the other patch myself later.

					-Alex


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2011-07-15 21:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30 20:25 [PATCH] xfsprogs: fix gcc 4.6 variable set but not used warnings Christoph Hellwig
2011-07-15 21:39 ` Alex Elder [this message]

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=1310765961.2921.98.camel@doink \
    --to=aelder@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox