From: Rich Johnston <rjohnston@sgi.com>
To: Eric Whitney <enwlinux@gmail.com>
Cc: <xfs@oss.sgi.com>, <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] xfstests: use native definition of O_DIRECT flag
Date: Tue, 5 Mar 2013 14:09:22 -0600 [thread overview]
Message-ID: <513650F2.8060406@sgi.com> (raw)
In-Reply-To: <20130226210322.GB5275@wallace>
This patch has been committed.
Thanks
--Rich
commit 5825ecd3b99ed8c177895d5e6a830133fed384ea
Author: Eric Whitney <enwlinux@gmail.com>
Date: Tue Feb 26 21:03:22 2013 +0000
xfstests: use native definition of O_DIRECT flag
The definition of O_DIRECT in src/trunc.c causes xfstest 125 to fail
when run on a Pandaboard. On ARM, the value used (0x040000) is
O_DIRECTORY rather than O_DIRECT as it is on x86. Prefer the
platform's
native definition of O_DIRECT supplied by fcntl.h if available. Also,
fix a couple of error messages to properly reflect their context.
Signed-off-by: Eric Whitney <enwlinux@gmail.com>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Rich Johnston <rjohnston@sgi.com>
prev parent reply other threads:[~2013-03-05 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 21:03 [PATCH] xfstests: use native definition of O_DIRECT flag Eric Whitney
2013-02-26 22:57 ` Dave Chinner
2013-03-05 20:09 ` Rich Johnston [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=513650F2.8060406@sgi.com \
--to=rjohnston@sgi.com \
--cc=enwlinux@gmail.com \
--cc=linux-ext4@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).