public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: xfs@oss.sgi.com
Subject: [PATCH 3/8] xfsprogs: remove the unused inst_t typedef
Date: Sun, 21 Jun 2015 11:21:59 +0200	[thread overview]
Message-ID: <1434878524-18176-4-git-send-email-hch@lst.de> (raw)
In-Reply-To: <1434878524-18176-1-git-send-email-hch@lst.de>

Signed-off-by: Christoph Hellwig <hch@lst.de>
---
 libxfs/libxfs_priv.h | 1 -
 1 file changed, 1 deletion(-)

diff --git a/libxfs/libxfs_priv.h b/libxfs/libxfs_priv.h
index 72fc4b3..37a86aa 100644
--- a/libxfs/libxfs_priv.h
+++ b/libxfs/libxfs_priv.h
@@ -96,7 +96,6 @@ extern char    *progname;
 #define ASSERT(ex) assert(ex)
 
 typedef __uint32_t		uint_t;
-typedef __uint32_t		inst_t;		/* an instruction */
 
 #ifndef EWRONGFS
 #define EWRONGFS	EINVAL
-- 
1.9.1

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2015-06-21  9:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-21  9:21 typedef cleanups for xfsprogs Christoph Hellwig
2015-06-21  9:21 ` [PATCH 1/8] xfsprogs: remove register keywords Christoph Hellwig
2015-06-21  9:21 ` [PATCH 2/8] xfsprogs: remove __psint_t and __psunsigned_t Christoph Hellwig
2015-06-23  5:42   ` Dave Chinner
2015-06-21  9:21 ` Christoph Hellwig [this message]
2015-06-21  9:22 ` [PATCH 4/8] xfsprogs: remove the uint_t typedef Christoph Hellwig
2015-06-21  9:22 ` [PATCH 5/8] xfsprogs: remove the uchar_t typedef Christoph Hellwig
2015-06-21  9:22 ` [PATCH 6/8] xfsprogs: remove boolean_t typedef Christoph Hellwig
2015-06-21  9:22 ` [PATCH 7/8] xfsprogs: remove non-Linux defintions for loff_t Christoph Hellwig
2015-06-21  9:22 ` [PATCH 8/8] xfsprogs: remove xfs_caddr_t Christoph Hellwig

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=1434878524-18176-4-git-send-email-hch@lst.de \
    --to=hch@lst.de \
    --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