From: Andrew Morton <akpm@osdl.org>
To: cmm@us.ibm.com
Cc: linux-fsdevel@vger.kernel.org, ext2-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 5/13] extents and 48bit ext3: sector_t type format string
Date: Thu, 8 Jun 2006 19:45:20 -0700 [thread overview]
Message-ID: <20060608194520.c7de1ee4.akpm@osdl.org> (raw)
In-Reply-To: <1149816130.4066.67.camel@dyn9047017069.beaverton.ibm.com>
On Thu, 08 Jun 2006 18:22:09 -0700
Mingming Cao <cmm@us.ibm.com> wrote:
>
>
> Define SECTOR_FMT to print sector_t in proper format
>
> ...
>
> #define HAVE_SECTOR_T
> typedef u64 sector_t;
> +#define SECTOR_FMT "%llu"
We did try this a few years ago, but I cannot for the life of me remember
our reasons for abandoning it :(
We ended up deciding that the best way of handling this is to open-code the
%lld and to typecast the argument to long long.
prev parent reply other threads:[~2006-06-09 2:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 1:22 [RFC 5/13] extents and 48bit ext3: sector_t type format string Mingming Cao
2006-06-09 2:45 ` Andrew Morton [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=20060608194520.c7de1ee4.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).