From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: William Lee Irwin III <wli@holomorphy.com>,
gibbs@scsiguy.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: ahc_linux_map_seg() compile/style/data corruption fixes
Date: Thu, 15 May 2003 18:36:31 +0200 [thread overview]
Message-ID: <20030515183631.B626@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20030514044934.GC29926@holomorphy.com>; from wli@holomorphy.com on Tue, May 13, 2003 at 09:49:34PM -0700
On Tue, May 13, 2003 at 09:49:34PM -0700, William Lee Irwin III wrote:
> (6) uint32_t used instead of u32 (contrary to Linux conventions)
Where is this stated?
uint32_t is C99 contrary to u32. It's valid
both in user and kernel space and allows to define ABI only once.
I use it both in user space and kernel code.
So I really need a _good_ reason, why this is against the
convention ;-)
Thanks & Regards
Ingo Oeser
prev parent reply other threads:[~2003-05-15 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 4:49 William Lee Irwin III
2003-05-14 5:37 ` William Lee Irwin III
2003-05-14 5:46 ` William Lee Irwin III
2003-05-14 6:18 ` Justin T. Gibbs
2003-05-14 6:21 ` William Lee Irwin III
2003-05-14 6:26 ` Justin T. Gibbs
2003-05-14 6:28 ` William Lee Irwin III
2003-05-15 16:36 ` Ingo Oeser [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=20030515183631.B626@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=wli@holomorphy.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
all inboxes | Powered by JetHome®