From: Sascha Hauer <s.hauer@pengutronix.de>
To: Dmitry Lavnikevich <d.lavnikevich@sam-solutions.net>
Cc: Grigory Milev <G.Milev@sam-solutions.com>,
barebox@lists.infradead.org,
Dmitry Lavnikevich <D.Lavnikevich@sam-solutions.com>
Subject: Re: [PATCH 1/5] mtd: Update internal API to support 64-bit device size
Date: Mon, 10 Mar 2014 08:20:03 +0100 [thread overview]
Message-ID: <20140310072003.GH17250@pengutronix.de> (raw)
In-Reply-To: <5319AA25.5050803@sam-solutions.net>
Hi Dmitry,
On Fri, Mar 07, 2014 at 02:14:45PM +0300, Dmitry Lavnikevich wrote:
> MTD internal API presently uses 32-bit values to represent device
> size. This patch updates them to 64-bits but leaves the external API
> unchanged.
>
> In general, changing from 32-bit to 64-bit values cause little
> or no changes to the majority of the code with the following
> exceptions:
> - printk message formats;
> - division and modulus of 64-bit values (mtd_div_by_wb,
> mtd_div_by_eb may be used in some of such cases).
>
> Was tested on phyFLEX i.MX6.
>
> Signed-off-by: Dmitry Lavnikevich <d.lavnikevich@sam-solutions.com>
> Signed-off-by: Grigory Milev <g.milev@sam-solutions.com>
Your patches look all good. Unfortunately I can't apply them because
your mailer wraps lines.
> diff --git a/drivers/mtd/core.c b/drivers/mtd/core.c
> index 6db1c6d..7efb03c 100644
> --- a/drivers/mtd/core.c
> +++ b/drivers/mtd/core.c
> @@ -397,7 +397,7 @@ int add_mtd_device(struct mtd_info *mtd, char
> *devname, int device_id)
> mtd->cdev.mtd = mtd;
> if (IS_ENABLED(CONFIG_PARAMETER)) {
> - dev_add_param_int_ro(&mtd->class_dev, "size", mtd->size, "%u");
> + dev_add_param_int_ro(&mtd->class_dev, "size", mtd->size, "%llu");
> dev_add_param_int_ro(&mtd->class_dev, "erasesize",
> mtd->erasesize, "%u");
For example here.
> flash->mtd.read = m25p80_read;
> diff --git a/drivers/mtd/devices/mtd_dataflash.c
Here is one space too much before 'diff'
> diff --git a/include/linux/mtd/mtd-abi.h b/include/linux/mtd/mtd-abi.h
> index 11d51e2..c1ba55b 100644
> --- a/include/linux/mtd/mtd-abi.h
> +++ b/include/linux/mtd/mtd-abi.h
> @@ -9,6 +9,8 @@
> #ifndef DOXYGEN_SHOULD_SKIP_THIS
> +#include <asm-generic/div64.h>
> +
Here also is one space too much.
Could you try resending it using git-send-email?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-03-10 7:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 11:14 Dmitry Lavnikevich
2014-03-10 7:20 ` Sascha Hauer [this message]
2014-03-10 8:02 ` Alexander Aring
2014-03-11 5:29 ` Sascha Hauer
2014-03-11 7:50 ` Alexander Aring
2014-03-12 20:28 ` Sascha Hauer
2014-03-10 11:37 ` Dmitry Lavnikevich
2014-03-10 11:39 Dmitry Lavnikevich
2014-03-12 20:28 ` Sascha Hauer
2014-03-12 20:51 ` Alexander Aring
2014-03-12 20:53 ` Sascha Hauer
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=20140310072003.GH17250@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=D.Lavnikevich@sam-solutions.com \
--cc=G.Milev@sam-solutions.com \
--cc=barebox@lists.infradead.org \
--cc=d.lavnikevich@sam-solutions.net \
/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