From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: [patch 1/1] dm: fix printk warnings about whether %lu/%Lu is right for sector_t
Date: Sat, 9 Oct 2004 02:04:46 +0200 [thread overview]
Message-ID: <200410090204.46720.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <Pine.LNX.4.60.0410082221340.26699@hermes-1.csi.cam.ac.uk>
On Friday 08 October 2004 23:57, Anton Altaparmakov wrote:
> On Fri, 8 Oct 2004, Paolo Giarrusso wrote:
> > On Friday 08 October 2004 22:11, Anton Altaparmakov wrote:
> > > On Fri, 8 Oct 2004, Andrew Morton wrote:
> > > > blaisorblade_spam@yahoo.it wrote:
> Yes I know in the kernel and on i386 it makes no difference, I said that
> already. But on some systems it does make a difference. I have seen it
> myself and I have had it reported.
> Thinking about it when I said
> architectures I possibly meant to say "other Unix flavours", I think one
> of the *BSDs was the one where I saw the difference between %L and %ll
> manifest itself.
Ok, I thought hardware archs - for other Unixes you're right.
Sorry for this and thanks for the lesson. Bye
> Sorry, it is not. I find it somewhat strange that you choose gcc and
> glibc to say what is correct... Ever heard of standards?!?
Yes, I heard them, I just never bought ISO standards.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
next prev parent reply other threads:[~2004-10-09 0:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 14:40 blaisorblade_spam
2004-10-08 19:12 ` Andrew Morton
2004-10-08 20:11 ` Anton Altaparmakov
2004-10-08 20:45 ` Paolo Giarrusso
2004-10-08 21:57 ` Anton Altaparmakov
2004-10-09 0:04 ` BlaisorBlade [this message]
2004-10-09 6:38 ` Anton Altaparmakov
2004-10-19 17:41 ` Alasdair G Kergon
2004-10-19 22:52 ` Andrew Morton
2004-10-21 15:27 ` Paolo Giarrusso
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=200410090204.46720.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=aia21@cam.ac.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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®