From: Theodore Tso <tytso@mit.edu>
To: Nick Dokos <nicholas.dokos@hp.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
Justin Maggard <jmaggard10@gmail.com>,
Andreas Dilger <adilger@sun.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] Fix counting routines in blknum.c to take/return __u32 counts.
Date: Sun, 6 Sep 2009 14:19:44 -0400 [thread overview]
Message-ID: <20090906181944.GN3055@mit.edu> (raw)
In-Reply-To: <10552.1252258878@gamaville.dokosmarshall.org>
On Sun, Sep 06, 2009 at 01:41:18PM -0400, Nick Dokos wrote:
>
> Apologies for the breakage, but I invariably do "make check" and I got
> no failures on the "make check" step (log appended). I probably should
> have ported them to a 32-bit platform and tested there but I did not. Is
> that where the failures arose?
Yeah, my laptop is still using an x86 32-bit userspace. One of these
days I'll update it to be 64-bit but for now it's nice for catching
these sorts of things.
- Ted
next prev parent reply other threads:[~2009-09-06 18:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 21:43 [PATCH] libext2fs: use ext2fs_blocks_count() in ext2fs_open2() Eric Sandeen
2009-09-02 5:59 ` Andreas Dilger
2009-09-02 6:05 ` Justin Maggard
2009-09-02 16:43 ` Eric Sandeen
2009-09-02 21:02 ` Nick Dokos
2009-09-02 21:28 ` Justin Maggard
2009-09-02 21:31 ` Eric Sandeen
2009-09-02 21:37 ` Nick Dokos
2009-09-02 21:43 ` Eric Sandeen
2009-09-02 21:45 ` Justin Maggard
2009-09-02 22:33 ` Eric Sandeen
2009-09-02 22:55 ` Andreas Dilger
2009-09-03 2:41 ` Eric Sandeen
2009-09-02 22:28 ` Theodore Tso
2009-09-02 23:12 ` Nick Dokos
2009-09-06 16:37 ` [PATCH] Fix counting routines in blknum.c to take/return __u32 counts Theodore Tso
2009-09-06 17:41 ` Nick Dokos
2009-09-06 18:19 ` Theodore Tso [this message]
2009-09-06 16:30 ` [PATCH] libext2fs: use ext2fs_blocks_count() in ext2fs_open2() Theodore Tso
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=20090906181944.GN3055@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=jmaggard10@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=nicholas.dokos@hp.com \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).