public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Felix Janda <felix.janda@posteo.de>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 4/4] Move to more stdint types
Date: Mon, 20 Jun 2016 08:54:10 +0200	[thread overview]
Message-ID: <20160620065410.GB431@nyan> (raw)
In-Reply-To: <20160620021226.GI26977@dastard>

Dave Chinner wrote:
> On Sat, Jun 18, 2016 at 04:53:30PM +0200, Felix Janda wrote:
> > The uint*_t and int*_t are defined by C99 and should be prefered
> > over the less portable __uint*_t and __int*_t variants. The
> > necessary <stdint.h> include is in platformdefs.h, which gets
> > included in most places via libxfs.h.
> > 
> > For now, only replace all __uint*_t types to uint*_t and likewise for
> > __int*_t outside the directories include/ and libxfs/.
> > 
> > Signed-off-by: Felix Janda <felix.janda@posteo.de>
> .....
> >  58 files changed, 502 insertions(+), 502 deletions(-)
> 
> Because of the amount of churn this will cause outstanding patchsets
> (e.g. the rmap/reflink work), this isn't the best time for us to be
> committing tree-wide cleanups like this. Once we get the major
> changes that are pending reviewed and committed I have no problems
> with making these changes, so perhaps you could regenerate the patch
> once those are merged?

Of course.

Thanks,
Felix

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

      reply	other threads:[~2016-06-20  6:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-18 14:53 [PATCH 4/4] Move to more stdint types Felix Janda
2016-06-20  2:12 ` Dave Chinner
2016-06-20  6:54   ` Felix Janda [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=20160620065410.GB431@nyan \
    --to=felix.janda@posteo.de \
    --cc=david@fromorbit.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