From: Nathan Scott <nathans@debian.org>
To: xfs@oss.sgi.com
Subject: Remove use of __psint_t in xfsdump as well
Date: Thu, 24 Sep 2015 19:17:44 -0400 (EDT) [thread overview]
Message-ID: <1482498135.42591149.1443136664561.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1054663595.42590503.1443136351475.JavaMail.zimbra@redhat.com>
Changes committed to git://oss.sgi.com/nathans/xfsdump.git master
Nathan Scott (1):
xfsdump: remove use of __psint_t, it is no longer available
common/drive_minrmt.c | 4 ++--
common/drive_scsitape.c | 4 ++--
common/drive_simple.c | 4 ++--
common/util.h | 4 ++--
debian/changelog | 6 ++++++
5 files changed, 14 insertions(+), 8 deletions(-)
commit 8a468340b2b0592daa553d722b4eff5997e18fc1
Author: Nathan Scott <nathans@debian.org>
Date: Fri Sep 25 09:11:31 2015 +1000
xfsdump: remove use of __psint_t, it is no longer available
Commit ee6cd73ed1e in xfsprogs switched __psint_t to the standards
conforming intptr_t type - we need to make the same change here in
xfsdump for builds using the latest xfsprogs headers.
Signed-off-by: Nathan Scott <nathans@debian.org>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
parent reply other threads:[~2015-09-24 23:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1054663595.42590503.1443136351475.JavaMail.zimbra@redhat.com>]
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=1482498135.42591149.1443136664561.JavaMail.zimbra@redhat.com \
--to=nathans@debian.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