ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: Tiger Yang <tiger.yang@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 4/4] ocfs2: Fixes two typos.
Date: Thu, 15 May 2008 16:52:08 +0800	[thread overview]
Message-ID: <1210841528-7769-4-git-send-email-tiger.yang@oracle.com> (raw)
In-Reply-To: <1210841528-7769-3-git-send-email-tiger.yang@oracle.com>

Signed-off-by: Tiger Yang <tiger.yang@oracle.com>
---
 configure.in |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/configure.in b/configure.in
index 14a0316..bd4fe02 100644
--- a/configure.in
+++ b/configure.in
@@ -233,7 +233,7 @@ KAPI_COMPAT_HEADERS="$KAPI_COMPAT_HEADERS $sysctl_compat_header"
 
 configfs_compat_header=""
 OCFS2_CHECK_KERNEL([configfs_depend_item() in configfs.h], configfs.h,
-  , configfs_compat_header="configfs.h", [configfs_depend_item()])
+  , configfs_compat_header="configfs.h", [configfs_depend_item(])
 KAPI_COMPAT_HEADERS="$KAPI_COMPAT_HEADERS $configfs_compat_header"
 
 REGISTER_SYSCTL_TWO_ARGS=
@@ -413,7 +413,7 @@ AC_SUBST(NO_SYSTEM_UTSNAME)
 
 HAS_MS_LOOP_NO_AOPS=
 OCFS2_CHECK_KERNEL([MS_LOOP_NO_AOPS flag defined], fs.h,
-  HAS_MS_LOOP_NO_AOPS==yes, , [MS_LOOP_NO_AOPS])
+  HAS_MS_LOOP_NO_AOPS=yes, , [MS_LOOP_NO_AOPS])
 AC_SUBST(HAS_MS_LOOP_NO_AOPS)
 
 HAS_FOPS_SENDFILE=
-- 
1.5.4.4

      reply	other threads:[~2008-05-15  8:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15  8:52 [Ocfs2-devel] [PATCH 1/4] ocfs2: Fixes pipe_buf_operations->pin switch to confirm in 2.6.23 Tiger Yang
2008-05-15  8:52 ` [Ocfs2-devel] [PATCH 2/4] ocfs2: Add inode_double_lock/unlock functions Tiger Yang
2008-05-15  8:52   ` [Ocfs2-devel] [PATCH 3/4] ocfs2: Add splice read/write support Tiger Yang
2008-05-15  8:52     ` Tiger Yang [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=1210841528-7769-4-git-send-email-tiger.yang@oracle.com \
    --to=tiger.yang@oracle.com \
    --cc=ocfs2-devel@oss.oracle.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).