From: Tim Hockin <thockin@hockin.org>
To: Eric Brower <ebrower@usa.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ethtool.h should use userspace-accessible types
Date: Thu, 11 Mar 2004 18:35:51 -0800 [thread overview]
Message-ID: <20040312023551.GA25331@hockin.org> (raw)
In-Reply-To: <40511868.4060109@usa.net>
On Thu, Mar 11, 2004 at 05:54:48PM -0800, Eric Brower wrote:
> Attached is a patch to 2.4's ethtool.h to use appropriate,
> userspace-accessible data types (__u8 and friends, rather than u8 and
> friends).
if we *know* the width of them, why don't we just use C99 standard types in
*both* places? I've never quite grokked why we need u8 and __u8 and all the
variants, when we now have uint8_t. I mean, at least it's standardized.
Anyone have a logical answer?
next prev parent reply other threads:[~2004-03-12 2:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 1:54 [PATCH] ethtool.h should use userspace-accessible types Eric Brower
2004-03-12 2:35 ` Tim Hockin [this message]
2004-03-12 4:57 ` Greg KH
2004-03-12 9:19 ` Tim Hockin
2004-03-12 16:25 ` Eric W. Biederman
2004-03-12 16:54 ` Jeff Garzik
2004-03-12 17:06 ` Eric W. Biederman
2004-03-12 21:48 ` Jonathan Lundell
2004-03-14 3:25 ` Matt Mackall
2004-03-15 21:24 ` Jonathan Lundell
2004-03-12 16:54 ` Jeff Garzik
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=20040312023551.GA25331@hockin.org \
--to=thockin@hockin.org \
--cc=ebrower@usa.net \
--cc=linux-kernel@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