public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Tinguely <tinguely@sgi.com>
To: rjohnston@sgi.com
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 3/3] xfstests: resolve compiler warnings
Date: Tue, 13 Nov 2012 14:24:49 -0600	[thread overview]
Message-ID: <50A2AC91.9080103@sgi.com> (raw)
In-Reply-To: <20121109132714.075017013@sgi.com>

On 11/09/12 07:24, rjohnston@sgi.com wrote:
> This patch resolves the following compiler/configure warnings:
>
>   configure: WARNING: unrecognized options: --enable-lib64
>   warning: 'xxxx' may be used uninitialized in this function [-Wuninitialized]
>   warning: variable 'xxx' set but not used [-Wunused-but-set-variable]
>   warning: call to function 'foo' without a real prototype [-Wunprototyped-calls]
>
> Signed-off-by: Rich Johnston<rjohnston@sgi.com>
>
> ---

Looks good.

Reviewed-by: Mark Tinguely <tinguely@sgi.com>

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

  reply	other threads:[~2012-11-13 20:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-09 13:23 [PATCH 0/3] xfstests: remove unused code and resolve warnings rjohnston
2012-11-09 13:23 ` [PATCH 1/3] xfstests: remove unsupported conditionals rjohnston
2012-11-13 20:23   ` Mark Tinguely
2012-11-21 10:13   ` Christoph Hellwig
2012-11-09 13:24 ` [PATCH 2/3] xfstests: remove unused conditional NO_XFS rjohnston
2012-11-13 20:24   ` Mark Tinguely
2012-11-21 10:13   ` Christoph Hellwig
2012-11-09 13:24 ` [PATCH 3/3] xfstests: resolve compiler warnings rjohnston
2012-11-13 20:24   ` Mark Tinguely [this message]
2012-11-21 10:14   ` Christoph Hellwig
2012-11-21 14:58 ` [PATCH 0/3] xfstests: remove unused code and resolve warnings Rich Johnston

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=50A2AC91.9080103@sgi.com \
    --to=tinguely@sgi.com \
    --cc=rjohnston@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