From: Eric Sandeen <sandeen@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>,
	xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: fix type usage
Date: Thu, 16 Nov 2017 13:45:43 -0600	[thread overview]
Message-ID: <d9ff8ef7-aadd-2668-680f-62ba0532cae1@redhat.com> (raw)
In-Reply-To: <20171116194344.GJ5119@magnolia>
On 11/16/17 1:43 PM, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
> 
> Be consistent about using uint32_t/uint8_t instead of u32/u8.  This is
> more so that we don't have to maintain /those/ types in xfsprogs.
> 
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Thanks Darrick.
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
> ---
>  fs/xfs/libxfs/xfs_iext_tree.c  |    2 +-
>  fs/xfs/libxfs/xfs_log_format.h |    4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/xfs/libxfs/xfs_iext_tree.c b/fs/xfs/libxfs/xfs_iext_tree.c
> index 343a942..19e546a 100644
> --- a/fs/xfs/libxfs/xfs_iext_tree.c
> +++ b/fs/xfs/libxfs/xfs_iext_tree.c
> @@ -302,7 +302,7 @@ xfs_iext_rec_cmp(
>  	xfs_fileoff_t		offset)
>  {
>  	uint64_t		rec_offset = rec->lo & XFS_IEXT_STARTOFF_MASK;
> -	u32			rec_len = rec->hi & XFS_IEXT_LENGTH_MASK;
> +	uint32_t		rec_len = rec->hi & XFS_IEXT_LENGTH_MASK;
>  
>  	if (rec_offset > offset)
>  		return 1;
> diff --git a/fs/xfs/libxfs/xfs_log_format.h b/fs/xfs/libxfs/xfs_log_format.h
> index 996f035..349d9f8 100644
> --- a/fs/xfs/libxfs/xfs_log_format.h
> +++ b/fs/xfs/libxfs/xfs_log_format.h
> @@ -274,7 +274,7 @@ struct xfs_inode_log_format {
>  	uint64_t		ilf_ino;	/* inode number */
>  	union {
>  		uint32_t	ilfu_rdev;	/* rdev value for dev inode*/
> -		u8		__pad[16];	/* unused */
> +		uint8_t		__pad[16];	/* unused */
>  	} ilf_u;
>  	int64_t			ilf_blkno;	/* blkno of inode buffer */
>  	int32_t			ilf_len;	/* len of inode buffer */
> @@ -295,7 +295,7 @@ struct xfs_inode_log_format_32 {
>  	uint64_t		ilf_ino;	/* inode number */
>  	union {
>  		uint32_t	ilfu_rdev;	/* rdev value for dev inode*/
> -		u8		__pad[16];	/* unused */
> +		uint8_t		__pad[16];	/* unused */
>  	} ilf_u;
>  	int64_t			ilf_blkno;	/* blkno of inode buffer */
>  	int32_t			ilf_len;	/* len of inode buffer */
> 
next prev parent reply	other threads:[~2017-11-16 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 19:43 [PATCH] xfs: fix type usage Darrick J. Wong
2017-11-16 19:45 ` Eric Sandeen [this message]
2017-11-17 16:47 ` 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=d9ff8ef7-aadd-2668-680f-62ba0532cae1@redhat.com \
    --to=sandeen@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.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).