From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Dong, Chuanxiao" <chuanxiao.dong@intel.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Yuan, Hang" <hang.yuan@intel.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"Woodhouse, David" <david.woodhouse@intel.com>,
"Gao, Yunpeng" <yunpeng.gao@intel.com>
Subject: Re: [PATCH] [MTD] include/linux/mtd/blktrans.h: fix wrong #blocks value reported by /proc/partitions
Date: Mon, 26 Jul 2010 07:45:34 +0300 [thread overview]
Message-ID: <1280119534.14917.9.camel@localhost> (raw)
In-Reply-To: <1280119248.14917.8.camel@localhost>
On Mon, 2010-07-26 at 07:40 +0300, Artem Bityutskiy wrote:
> On Thu, 2010-07-22 at 17:34 +0800, Dong, Chuanxiao wrote:
> > Hi
> > I found /proc/partitions file will report a wrong block numbers when I use a 8G
> > NAND which has a larger than 4G partition. So here is a patch to fix this problem.
> > Details are in below comments.
> > Please review it.
> > Thanks all.
>
> Pushed to l2-mtd-2.6.git / master, thanks.
Umm, no, kicked out. It introduces warnings:
drivers/mtd/inftlcore.c: In function ‘inftl_add_mtd’:
drivers/mtd/inftlcore.c:112: warning: format ‘%lx’ expects type ‘long unsigned int’, but argument 2 has type ‘uint64_t’
CC [M] drivers/mtd/nftlcore.o
CC [M] drivers/mtd/nftlmount.o
drivers/mtd/nftlcore.c: In function ‘nftl_add_mtd’:
drivers/mtd/nftlcore.c:101: warning: format ‘%lx’ expects type ‘long unsigned int’, but argument 2 has type ‘uint64_t’
Please, use 'unsigned long long' and %llx modifiers in the prints.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-07-26 4:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 9:34 [PATCH] [MTD] include/linux/mtd/blktrans.h: fix wrong #blocks value reported by /proc/partitions Dong, Chuanxiao
2010-07-26 4:40 ` Artem Bityutskiy
2010-07-26 4:45 ` 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=1280119534.14917.9.camel@localhost \
--to=dedekind1@gmail.com \
--cc=chuanxiao.dong@intel.com \
--cc=david.woodhouse@intel.com \
--cc=dwmw2@infradead.org \
--cc=hang.yuan@intel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=yunpeng.gao@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.