From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
xfs <linux-xfs@vger.kernel.org>,
Eric Sandeen <sandeen@redhat.com>
Subject: Re: [PATCH 1/3] xfs: remove double-underscore integer types
Date: Wed, 17 May 2017 23:31:09 -0700 [thread overview]
Message-ID: <20170518063109.GB722@infradead.org> (raw)
In-Reply-To: <20170518060158.GP17542@dastard>
> I'm not sure that this is entirely correct when it comes to sparse
> endian notations or the way the __ types were intended to be used.
> ISTR we used the __ types were originally for the in-memory endian
> converted variable definitions that shadowed the on-disk structures.
> The cleanup plan I was planning to do was to convert these all to
> the linux kernel definitions of __[s,u][8,16,32,64] so it was clear
> they shadow on disk structures of specific sizes.
>
> Once that was done, everything else could be converted to c99 types
> (like you've done above) and then we'd be free of all the old
> __[u]int*_t types....
Sparse doesn't care - what matters there are the __be* and __le*
types.
Otherwise it's just a decision if we want to use C99 or Linux types,
and if we want to use Linux types if we want to use the __-prefixed
ones to avoid name collisions in userspace.
I'm fine either way - I'm used to typing uXX so that'd be my first
preference, but the uintX_t is a close second, so I'd be perfectly
fine with this patch:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2017-05-18 6:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 1:26 [RFCRAP 0/3?] xfs: OH GOD MY EYES! Darrick J. Wong
2017-05-18 1:30 ` [PATCH 1/3] xfs: remove double-underscore integer types Darrick J. Wong
2017-05-18 6:01 ` Dave Chinner
2017-05-18 6:21 ` Darrick J. Wong
2017-05-18 6:31 ` Christoph Hellwig [this message]
2017-05-18 1:31 ` [PATCH 2/3] xfsprogs: " Darrick J. Wong
2017-05-18 6:32 ` Christoph Hellwig
2017-05-23 2:48 ` Darrick J. Wong
2017-05-23 2:24 ` Eric Sandeen
2017-05-18 1:32 ` [PATCH 3/3] xfs: freeze rw filesystems just prior to reboot Darrick J. Wong
2017-05-18 6:28 ` Christoph Hellwig
2017-05-18 8:34 ` Dave Chinner
2017-05-18 22:30 ` Darrick J. Wong
2017-05-19 19:09 ` Chris Murphy
2017-05-19 21:00 ` Darrick J. Wong
2017-05-20 0:27 ` Chris Murphy
2017-05-22 2:07 ` Dave Chinner
[not found] ` <20170522020112.GV17542@dastard>
2017-05-22 20:46 ` Chris Murphy
2017-05-23 3:56 ` Chris Murphy
2017-05-23 4:04 ` Eric Sandeen
2017-05-23 11:44 ` Dave Chinner
2017-05-24 3:19 ` Dave Chinner
2017-05-24 8:06 ` Chris Murphy
2017-05-24 6:22 ` Chris Murphy
2017-05-24 6:25 ` Chris Murphy
2017-05-24 23:13 ` Dave Chinner
2017-05-25 0:03 ` Dave Chinner
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=20170518063109.GB722@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).