From: Dave Chinner <david@fromorbit.com>
To: Li Xi <pkuelelixi@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>, Andreas Dilger <adilger@dilger.ca>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"hch@infradead.org" <hch@infradead.org>,
Dmitry Monakhov <dmonakhov@openvz.org>,
John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [v14 3/4] ext4: adds FS_IOC_FSSETXATTR/FS_IOC_FSGETXATTR interface support
Date: Thu, 30 Apr 2015 08:07:17 +1000 [thread overview]
Message-ID: <20150429220717.GX15810@dastard> (raw)
In-Reply-To: <CAPTn0cDZ3rHBxo2rQCWM=cZsjrL3QJUAkbkaj1ax3b72OUn0Rg@mail.gmail.com>
On Wed, Apr 29, 2015 at 07:45:40PM +0800, Li Xi wrote:
> On Wed, Apr 29, 2015 at 3:59 PM, Jan Kara <jack@suse.cz> wrote:
> > Hi,
> >
> > On Wed 29-04-15 13:49:08, Li Xi wrote:
> >> Thanks for the advices. I tried to run latest xfstests again. However,
> > Dave actually asked you to update 'xfsprogs' not xfstests. Not that
> > updating xfstests would be a wrong thing to do but you still need to update
> > xfsprogs for xfstests to be able to run some tests. But that's unrelated to
> > the oops you reported below.
> Understood. I updated both xfstests and xfsprogs to the latest version from git
> repository. However, I didn't update xfsdump because of a build failure caused
> by missing definitons of 'min' and 'max'
The /usr/include/xfs header files are stale. Upgrade your
xfslibs-dev package, if there is one for your distro.
And, please, report package build failures to the appropriate list,
next time, rather than ignoring them?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2015-04-29 22:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 18:56 [v14 0/4] ext4: add project quota support Li Xi
[not found] ` <1429728997-21464-1-git-send-email-lixi-LfVdkaOWEx8@public.gmane.org>
2015-04-22 18:56 ` [v14 1/4] ext4: adds project ID support Li Xi
2015-04-22 18:56 ` [v14 4/4] ext4: cleanup inode flag definitions Li Xi
2015-04-22 19:45 ` [v14 0/4] ext4: add project quota support Andreas Dilger
2015-04-22 18:56 ` [v14 2/4] ext4: adds " Li Xi
2015-04-22 18:56 ` [v14 3/4] ext4: adds FS_IOC_FSSETXATTR/FS_IOC_FSGETXATTR interface support Li Xi
2015-04-24 16:40 ` Jan Kara
[not found] ` <1429728997-21464-4-git-send-email-lixi-LfVdkaOWEx8@public.gmane.org>
2015-04-26 23:20 ` Dave Chinner
2015-04-28 2:01 ` Li Xi
[not found] ` <CAPTn0cAHOHP060cW8k0-HnyfKdVaUwAVOyLZU43AXtECK6_EaA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-28 4:43 ` Dave Chinner
2015-04-29 5:49 ` Li Xi
2015-04-29 7:59 ` Jan Kara
2015-04-29 11:45 ` Li Xi
2015-04-29 22:07 ` Dave Chinner [this message]
2015-06-04 15:29 ` Li Xi
2015-06-05 7:45 ` Dmitry Monakhov
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=20150429220717.GX15810@dastard \
--to=david@fromorbit.com \
--cc=adilger@dilger.ca \
--cc=dmonakhov@openvz.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=john.stultz@linaro.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pkuelelixi@gmail.com \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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