From: Eric Sandeen <sandeen@sandeen.net>
To: Eric Sandeen <sandeen@sandeen.net>,
Christoph Hellwig <hch@infradead.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: check for dmapi headers
Date: Sat, 25 Oct 2008 22:01:48 -0500 [thread overview]
Message-ID: <4903DD9C.60000@sandeen.net> (raw)
In-Reply-To: <20081025233231.GB11948@disturbed>
Dave Chinner wrote:
> On Sat, Oct 25, 2008 at 03:19:28PM -0500, Eric Sandeen wrote:
>> Christoph Hellwig wrote:
>>> On Sat, Oct 25, 2008 at 01:18:35PM -0500, Eric Sandeen wrote:
>>>> I'm no autoconf wizard, but I think this does the trick to allow
>>>> xfstests build to succeed when dmapi headers are missing, as
>>>> they probably will be for any distro that doesn't ship with
>>>> dmapi in the kernel, or dmapi userspace.
>>>>
>>>> AFAIK the dmapi-related tests all fail gracefully with "not run."
>>> Looks sane to me, although the dmapi library can of course be shipped
>>> without kernel support - it's just rather useless that way :)
>> true, but very, very little motivation for that :)
>
> $ dpkg -l libdm0\*
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
> ||/ Name Version Description
> +++-==================-==================-====================================================
> ii libdm0 2.2.8-1 Data Management API runtime environment
> ii libdm0-dev 2.2.8-1 Data Management API static libraries and headers
> $
I meant my motivation ;)
-Eric
prev parent reply other threads:[~2008-10-26 3:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-25 18:18 [PATCH] xfstests: check for dmapi headers Eric Sandeen
2008-10-25 20:18 ` Christoph Hellwig
2008-10-25 20:19 ` Eric Sandeen
2008-10-25 23:32 ` Dave Chinner
2008-10-26 3:01 ` Eric Sandeen [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=4903DD9C.60000@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hch@infradead.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