public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: Lepton Wu <ytht.net@gmail.com>, dwmw2@infradead.org
Cc: computersforpeace@gmail.com, boris.brezillon@free-electrons.com,
	richard@nod.at, cyrille.pitchen@atmel.com,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mtd: Fix mtdblock for >4GB MTD devices
Date: Mon, 27 Feb 2017 10:31:58 +0100	[thread overview]
Message-ID: <254c5202-64cd-ddae-2e76-8db6a4486b80@gmail.com> (raw)
In-Reply-To: <20170222021558.710-1-ytht.net@gmail.com>

On 02/22/2017 03:15 AM, Lepton Wu wrote:
> Change to use loff_t instead of unsigned long in some functions
> to make sure mtdblock can handle offset bigger than 4G in 32 bits mode.
> 
> Signed-off-by: Lepton Wu <ytht.net@gmail.com>
> ---
>  Changes in v2:
>   - Make the commit message more clearer and fix some format issues.
> 
>  drivers/mtd/mtdblock.c    | 35 ++++++++++++++++++-----------------
>  drivers/mtd/mtdblock_ro.c |  4 ++--
>  2 files changed, 20 insertions(+), 19 deletions(-)
> 
> diff --git a/drivers/mtd/mtdblock.c b/drivers/mtd/mtdblock.c
> index bb4c14f83c75..373c0edca803 100644
> --- a/drivers/mtd/mtdblock.c
> +++ b/drivers/mtd/mtdblock.c
> @@ -61,8 +61,8 @@ static void erase_callback(struct erase_info *done)
>  	wake_up(wait_q);
>  }
>  
> -static int erase_write (struct mtd_info *mtd, unsigned long pos,
> -			int len, const char *buf)
> +static int erase_write(struct mtd_info *mtd, loff_t pos, int len,
> +		       const char *buf)

Can the length be 64bit too now ?

[...]

-- 
Best regards,
Marek Vasut

  reply	other threads:[~2017-02-27 10:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22  2:15 [PATCH v2] mtd: Fix mtdblock for >4GB MTD devices Lepton Wu
2017-02-27  9:31 ` Marek Vasut [this message]
2017-03-01  4:14   ` lepton
2017-03-13  5:07     ` Marek Vasut

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=254c5202-64cd-ddae-2e76-8db6a4486b80@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=cyrille.pitchen@atmel.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=ytht.net@gmail.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