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 some warnings
Date: Fri, 12 Feb 2010 15:53:40 -0600	[thread overview]
Message-ID: <1266011620.1865.17.camel@doink1> (raw)
In-Reply-To: <20100212212329.GA6084@infradead.org>

On Fri, 2010-02-12 at 16:23 -0500, Christoph Hellwig wrote:
> On Fri, Feb 12, 2010 at 02:49:45PM -0600, Alex Elder wrote:
> > Fix a couple of build warnings.
> > 
> > Signed-off-by: Alex Elder <aelder@sgi.com>
> > 
> > ---
> >  ltp/fsx.c    |    2 +-
> >  src/loggen.c |    1 +
> >  2 files changed, 2 insertions(+), 1 deletion(-)
> 
> Looks good, but it's actually for xfstests, not xfsdump as said in
> the subject line.
> 
> Reviewed-by: Christoph Hellwig <hch@lst.de>

I will fix the subject line before I commit.
Thanks.

					-Alex

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

      reply	other threads:[~2010-02-12 21:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12 20:49 [PATCH] xfsprogs: fix some warnings Alex Elder
2010-02-12 21:23 ` Christoph Hellwig
2010-02-12 21:53   ` 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=1266011620.1865.17.camel@doink1 \
    --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