From: Artem Bityutskiy <dedekind@infradead.org>
To: "Randy.Dunlap" <randy.dunlap@oracle.com>
Cc: akpm <akpm@osdl.org>, Ben Dooks <ben@fluff.org>,
dwmw2@infradead.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] MTD: fix printk format warning
Date: Tue, 24 Oct 2006 19:57:13 +0300 [thread overview]
Message-ID: <1161709033.3260.188.camel@sauron> (raw)
In-Reply-To: <453E315B.8090801@oracle.com>
On Tue, 2006-10-24 at 08:29 -0700, Randy.Dunlap wrote:
> which I suppose is what Artem missed. I.e., it's not always unsigned long.
> However, I won't deny that gcc seems odd here.
I just wanted to say that (unsigned long)a - b + 1 has "unsigned long"
type even if "a" and "b" are u32 or u64. I would have understood you if
you had said that you cut "a" because of the u64->unsigned long casting,
but I understood that the rationale for the change was to fix print
format warning...
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2006-10-24 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 4:48 [PATCH] MTD: fix printk format warning Randy Dunlap
2006-10-24 9:24 ` Artem Bityutskiy
2006-10-24 10:02 ` Ben Dooks
2006-10-24 15:29 ` Randy.Dunlap
2006-10-24 16:57 ` Artem Bityutskiy [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=1161709033.3260.188.camel@sauron \
--to=dedekind@infradead.org \
--cc=akpm@osdl.org \
--cc=ben@fluff.org \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=randy.dunlap@oracle.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