From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, peter@chubb.wattle.id.au
Cc: akpm@digeo.com, linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] struct loop_info64
Date: Wed, 23 Apr 2003 10:20:39 +0200 (MEST) [thread overview]
Message-ID: <UTC200304230820.h3N8Kd501822.aeb@smtp.cwi.nl> (raw)
> it's *usually* better not to use int or long,
> but to use explicitly-sized types
The version that was committed by Linus only uses explicit types.
Andries
[I get requests for an additional field lo_size, so perhaps
this struct will still change a little.]
next reply other threads:[~2003-04-23 8:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 8:20 Andries.Brouwer [this message]
[not found] <759098236@toto.iv>
2003-04-23 0:43 ` Peter Chubb
-- strict thread matches above, loose matches on Subject: below --
2003-04-18 17:19 Andries.Brouwer
2003-04-18 17:50 ` Linus Torvalds
2003-04-18 13:04 Andries.Brouwer
2003-04-18 16:26 ` Linus Torvalds
2003-04-18 16:55 ` Greg KH
2003-04-18 17:55 ` Linus Torvalds
2003-04-18 18:06 ` Greg KH
2003-04-18 19:12 ` Kai Germaschewski
2003-04-19 4:54 ` Rusty Russell
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=UTC200304230820.h3N8Kd501822.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
--cc=torvalds@transmeta.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®