Re: [PATCH 1/1][v2] IFC: Change IO accessor based on endianness

[Brian Norris <computersforpeace@gmail.com>]

On Mon, Nov 03, 2014 at 05:22:46PM -0600, Scott Wood wrote:
> On Mon, 2014-10-20 at 11:41 +0530, Jaiprakash Singh wrote:
> > From: Jaiprakash Singh <b44839@freescale.com>
> > 
> > IFC registers can be of type Little Endian
> > or big Endian depending upon Freescale SoC.
> > Here SoC defines the register type of
> > IFC IP.So update accessors functions with
> > common IFC accessors functions to take
> > care both type of endianness.
> > 
> > IFC IO accressor are set at run time based
> > on IFC IP registers endianness.IFC node in
> > DTS file contains information about
> > endianness.
> > 
> > Signed-off-by: Jaiprakash Singh <b44839@freescale.com>
> > ---
> > Changes for v2
> > 	- Moved IFC accessor function to fsl_ifc.h
> > 	from fsl_ifc.c and make them inline static
> > 
> > .../bindings/memory-controllers/fsl/ifc.txt        |    2 +
> >  drivers/memory/fsl_ifc.c                           |   72 ++++++----
> >  drivers/mtd/nand/fsl_ifc_nand.c                    |  151 +++++++++++---------
> >  include/linux/fsl_ifc.h                            |   42 ++++++
> >  4 files changed, 167 insertions(+), 100 deletions(-)
> 
> Given that this spans MTD and non-MTD files, whose tree should this go
> through?

I already have one patch that touches these same files:

  http://git.infradead.org/l2-mtd.git/commitdiff/096916610f415e07cfe71d71a391011c617be5ed

I don't actually see a MAINTAINERS entry for most of drivers/memory/, so
I didn't think that was a problem. If the (fixed) full patch can be
based on l2-mtd.git and submitted with linux-mtd@infradead.org in CC, I
can consider taking it, pending proper review.

Brian