From: Eliot Blennerhassett <linux@audioscience.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: linux vs c99 fixed width types
Date: Fri, 02 Jul 2010 13:13:26 +1200 [thread overview]
Message-ID: <4C2D3D36.3020009@audioscience.com> (raw)
Hi Takashi, & list
it is quite likely that we will be moving our own codebase to use the
C99 fixed width types rather than our own e.g. uint32_t vs HW32 etc.
Currently HW32 is translated into u32 before I submit patches to you.
Should I do the same for the C99 types, or let them pass through unaltered?
regards
--
Eliot Blennerhassett
AudioScience Inc.
next reply other threads:[~2010-07-02 1:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 1:13 Eliot Blennerhassett [this message]
2010-07-02 10:28 ` linux vs c99 fixed width types Mark Brown
2010-07-05 9:29 ` Takashi Iwai
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=4C2D3D36.3020009@audioscience.com \
--to=linux@audioscience.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.