From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: don't run 122 if required headers aren't found
Date: Wed, 3 Jun 2009 15:35:54 -0400 [thread overview]
Message-ID: <20090603193554.GA4516@infradead.org> (raw)
In-Reply-To: <20090603175103.GA4538@infradead.org>
On Wed, Jun 03, 2009 at 01:51:03PM -0400, Christoph Hellwig wrote:
> On Wed, Jun 03, 2009 at 12:17:10PM -0500, Eric Sandeen wrote:
> > Now that libxfs etc is optional, 122 (which compiles on the fly)
> > is failing if those extra headers are missing.
>
> Oh, the great 122 tests. Indeed without all the headers defining
> the structures we can't actually check their size.
>
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Umm, should be:
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-06-03 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 17:17 [PATCH] xfstests: don't run 122 if required headers aren't found Eric Sandeen
2009-06-03 17:51 ` Christoph Hellwig
2009-06-03 19:35 ` Christoph Hellwig [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=20090603193554.GA4516@infradead.org \
--to=hch@infradead.org \
--cc=sandeen@redhat.com \
--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