From: Stefan Weil <sw@weilnetz.de>
To: Peter Maydell <peter.maydell@linaro.org>,
Jan Vesely <jano.vesely@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
QEMU Trivial <qemu-trivial@nongnu.org>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] configure: Check if struct fsxattr is available from linux header
Date: Fri, 29 Apr 2016 15:56:29 +0200 [thread overview]
Message-ID: <5723680D.2050601@weilnetz.de> (raw)
In-Reply-To: <CAFEAcA-yNp8wGnyzMrTu=28g4vYPv-5F-PJ4aeHq8xSnxRZLkA@mail.gmail.com>
Am 29.04.2016 um 15:54 schrieb Peter Maydell:
> This means we'll build with a HAVE_FSXATTR define set, but
> nothing in the tree tries to use that as far as I can tell:
> "git grep HAVE_FSXATTR" returns no matches. What am I missing?
>
> thanks
> -- PMM
>
It's used by the system headers:
/usr/include/xfs/xfs_fs.h:#ifndef HAVE_FSXATTR
Stefan
next prev parent reply other threads:[~2016-04-29 13:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 13:07 [Qemu-devel] [PATCH] configure: Check if struct fsxattr is available from linux header Jan Vesely
2016-04-29 13:54 ` Stefan Weil
2016-04-29 13:54 ` Peter Maydell
2016-04-29 13:56 ` Stefan Weil [this message]
2016-04-29 14:00 ` Peter Maydell
2016-04-29 14:31 ` Stefan Weil
2016-04-29 14:49 ` Peter Maydell
2016-04-29 17:14 ` Jan Vesely
2016-04-29 17:15 ` [Qemu-devel] [PATCH v2] " Jan Vesely
2016-05-02 12:07 ` Peter Maydell
2016-05-02 12:18 ` [Qemu-devel] [Qemu-trivial] [PATCH] " Michael Tokarev
2016-05-02 12:30 ` Peter Maydell
[not found] <1458436706-20743-1-git-send-email-jano.vesely@gmail.com>
2016-04-12 21:09 ` [Qemu-devel] " Jan Vesely
2016-04-29 0:54 ` Jan Vesely
2016-04-29 7:52 ` Markus Armbruster
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=5723680D.2050601@weilnetz.de \
--to=sw@weilnetz.de \
--cc=armbru@redhat.com \
--cc=jano.vesely@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
/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).