From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs-oss <xfs@oss.sgi.com>, fstests@vger.kernel.org
Subject: Re: [PATCH] xfs/279: use MKFS_XFS_PROG, not hardcoded path
Date: Mon, 16 Jun 2014 02:34:40 -0700 [thread overview]
Message-ID: <20140616093440.GA26172@infradead.org> (raw)
In-Reply-To: <539B68D2.2000300@sandeen.net>
On Fri, Jun 13, 2014 at 04:10:42PM -0500, Eric Sandeen wrote:
> I'm really not sure why this wasn't this way from the start.
> On some systems it's in /usr/sbin, and the test fails.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: fstests@vger.kernel.org, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfs/279: use MKFS_XFS_PROG, not hardcoded path
Date: Mon, 16 Jun 2014 02:34:40 -0700 [thread overview]
Message-ID: <20140616093440.GA26172@infradead.org> (raw)
In-Reply-To: <539B68D2.2000300@sandeen.net>
On Fri, Jun 13, 2014 at 04:10:42PM -0500, Eric Sandeen wrote:
> I'm really not sure why this wasn't this way from the start.
> On some systems it's in /usr/sbin, and the test fails.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-06-16 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 21:10 [PATCH] xfs/279: use MKFS_XFS_PROG, not hardcoded path Eric Sandeen
2014-06-13 21:10 ` Eric Sandeen
2014-06-16 9:34 ` Christoph Hellwig [this message]
2014-06-16 9:34 ` Christoph Hellwig
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=20140616093440.GA26172@infradead.org \
--to=hch@infradead.org \
--cc=fstests@vger.kernel.org \
--cc=sandeen@sandeen.net \
--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.