public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Alex Elder <aelder@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/5] xfstests: dmapi: eliminate all build warnings
Date: Thu, 28 Apr 2011 12:15:41 +1000	[thread overview]
Message-ID: <20110428021541.GN12436@dastard> (raw)
In-Reply-To: <1303413073-24173-1-git-send-email-aelder@sgi.com>

On Thu, Apr 21, 2011 at 02:11:08PM -0500, Alex Elder wrote:
> I'm hoping the Nth time is a charm...
> 
> This series eliminates all build warnings that come out of building
> things under the dmapi/ subdirectory.  I'm using gcc 4.x (x < 6) on
> several platforms, including i386, x86_64, and ia64 architectures.
> 
> I have sent these a couple times before; they are unmodified from
> the last time I sent them out.  I am omitting the summary of the
> types of warnings and how they got resolved this time around.

Nothing jumps out as wrong to me. Looks good.


Reviewed-by: Dave Chinner <dchinner@redhat.com>

-- 
Dave Chinner
david@fromorbit.com

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

      parent reply	other threads:[~2011-04-28  2:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21 19:11 [PATCH 0/5] xfstests: dmapi: eliminate all build warnings Alex Elder
2011-04-21 19:11 ` [PATCH 1/5] xfstests: eliminate some warnings under dmapi/src Alex Elder
2011-04-21 19:11   ` [PATCH 2/5] xfstests: eliminate warnings under dmapi/src/suite1/cmd (1) Alex Elder
2011-04-21 19:11   ` [PATCH 3/5] xfstests: eliminate warnings under dmapi/src/suite1/cmd (2) Alex Elder
2011-04-21 19:11   ` [PATCH 4/5] xfstests: eliminate warnings under dmapi/src/suite1/cmd (3) Alex Elder
2011-04-21 19:11   ` [PATCH 5/5] xfstests: eliminate warnings under dmapi/src/suite2/src Alex Elder
2011-04-28  2:15 ` Dave Chinner [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=20110428021541.GN12436@dastard \
    --to=david@fromorbit.com \
    --cc=aelder@sgi.com \
    --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