From: Eryu Guan <eguan@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
david@fromorbit.com, linux-btrfs@vger.kernel.org,
fstests@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH v2] xfs: test attr_list_by_handle cursor iteration
Date: Fri, 12 Aug 2016 11:14:00 +0800 [thread overview]
Message-ID: <20160812031400.GR27776@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20160811174855.GD31540@infradead.org>
On Thu, Aug 11, 2016 at 10:48:55AM -0700, Christoph Hellwig wrote:
> On Thu, Aug 04, 2016 at 12:24:48PM +0800, Eryu Guan wrote:
> > I have to replace false/true with 0/1 to build it on RHEL6. I can fix it
> > at commit time if there's no other major updates.
>
> Simply including <stdbool.h> would fix that on RHEL6, wouldn't it?
Yes, including <stdbool.h> fixes the build failure on RHEL6, another
option is to replace all bool with int, as mentioned in my first review
email. And Darric chose the "int" way in v2 but only updated the
function definition and forgot to update the callers (still passing
true/false, not 1/0).
Thanks for the review!
Eryu
WARNING: multiple messages have this Message-ID (diff)
From: Eryu Guan <eguan@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com, fstests@vger.kernel.org,
linux-btrfs@vger.kernel.org,
"Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: [PATCH v2] xfs: test attr_list_by_handle cursor iteration
Date: Fri, 12 Aug 2016 11:14:00 +0800 [thread overview]
Message-ID: <20160812031400.GR27776@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20160811174855.GD31540@infradead.org>
On Thu, Aug 11, 2016 at 10:48:55AM -0700, Christoph Hellwig wrote:
> On Thu, Aug 04, 2016 at 12:24:48PM +0800, Eryu Guan wrote:
> > I have to replace false/true with 0/1 to build it on RHEL6. I can fix it
> > at commit time if there's no other major updates.
>
> Simply including <stdbool.h> would fix that on RHEL6, wouldn't it?
Yes, including <stdbool.h> fixes the build failure on RHEL6, another
option is to replace all bool with int, as mentioned in my first review
email. And Darric chose the "int" way in v2 but only updated the
function definition and forgot to update the callers (still passing
true/false, not 1/0).
Thanks for the review!
Eryu
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-08-12 3:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 23:52 [PATCH] xfs: test attr_list_by_handle cursor iteration Darrick J. Wong
2016-08-02 23:52 ` Darrick J. Wong
2016-08-03 4:47 ` Eryu Guan
2016-08-03 4:47 ` Eryu Guan
2016-08-03 22:42 ` Darrick J. Wong
2016-08-03 22:42 ` Darrick J. Wong
2016-08-03 22:51 ` [PATCH v2] " Darrick J. Wong
2016-08-03 22:51 ` Darrick J. Wong
2016-08-04 4:24 ` Eryu Guan
2016-08-04 4:24 ` Eryu Guan
2016-08-11 17:48 ` Christoph Hellwig
2016-08-11 17:48 ` Christoph Hellwig
2016-08-12 3:14 ` Eryu Guan [this message]
2016-08-12 3:14 ` Eryu Guan
2016-08-05 2:03 ` [PATCH v3] " Darrick J. Wong
2016-08-05 2:03 ` Darrick J. Wong
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=20160812031400.GR27776@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-btrfs@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 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.