From: Keith Owens <kaos@ocs.com.au>
To: Christoph Hellwig <hch@ns.caldera.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: daddr_t is inconsistent and barely used
Date: Thu, 16 Aug 2001 13:14:20 +1000 [thread overview]
Message-ID: <10589.997931660@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Thu, 16 Aug 2001 04:57:34 +0200." <200108160257.f7G2vYA18080@ns.caldera.de>
On Thu, 16 Aug 2001 04:57:34 +0200,
Christoph Hellwig <hch@ns.caldera.de> wrote:
>In article <9980.997929632@kao2.melbourne.sgi.com> you wrote:
>> daddr_t is barely used in the kernel. 2.4.8.
>>
>> The use of daddr_t in freevxfs may give different in core and disk
>> layouts on different machines. Is that intended?.
>
>No, it may not. Please double check.
That is why I said "may". It seemed puzzling that freevxfs used
vx_daddr_t for almost everything but daddr_t for a couple of fields.
An inconsistency with no obvious reason.
next prev parent reply other threads:[~2001-08-16 3:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 2:40 daddr_t is inconsistent and barely used Keith Owens
2001-08-16 2:57 ` Christoph Hellwig
2001-08-16 3:14 ` Keith Owens [this message]
2001-08-16 3:21 ` Christoph Hellwig
2001-08-16 3:52 ` Albert D. Cahalan
2001-08-16 3:59 ` Christoph Hellwig
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=10589.997931660@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=hch@ns.caldera.de \
--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