[PATCH v2 0/5] unconfuse get_unmapped_area and point/unpoint driver methods

[Chris Brandt]

On Tuesday, October 17, 2017 1, Nicolas Pitre wrote:
> This series improves or implements the point and unpoint driver methods
> and reimplements mtd_get_unmapped_area() in terms of those. Because
> mtd->_point() provides a superset of what mtd->_get_unmapped_area() does
> then there is no reason for having both. Or worse: having one but not
> the other.
> 
> This is motivated by my work on XIP cramfs for both MMU and !MMU systems
> where I do need the more complete point functionality. And it just looks
> like the right thing to do.
> 
> This is also available on top of Linux v4.14-rc3 via git here:
> 
>   http://git.linaro.org/people/nicolas.pitre/linux mtd_point
> 
> 
> Changes from v1:
> 
> - Fix retlen computation in mtdram.c:ram_point().
> 
> - Added Richard Weinberger's REviewd-by tags.
> 
> 
> diffstat:
> 
>  drivers/mtd/chips/map_ram.c  | 34 ++++++++++++++++++++--------------
>  drivers/mtd/chips/map_rom.c  | 34 +++++++++++++++++++++-------------
>  drivers/mtd/devices/mtdram.c | 36 ++++++++++++++++++++++--------------
>  drivers/mtd/mtdconcat.c      | 27 ---------------------------
>  drivers/mtd/mtdcore.c        | 17 ++++++++++++-----
>  drivers/mtd/mtdpart.c        | 14 --------------
>  include/linux/mtd/mtd.h      |  4 ----
>  7 files changed, 75 insertions(+), 91 deletions(-)

I was able to boot my system with the following kernel options:

  "rootfstype=cramfs root=mtd:rootfs_xipcramfs"

This meant the cramfs image was one where the executable code pages 
remained in flash.


Therefore, for this MTD series, applied on top of the file system series 
"[PATCH v6 0/4] cramfs refresh for embedded usage":

Tested-by: Chris Brandt <chris.brandt at renesas.com>