From: Scott Wood <scottwood@freescale.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: B07421@freescale.com, linux-mtd@lists.infradead.org,
gregkh@linuxfoundation.org, arnd@arndb.de,
Jaiprakash Singh <b44839@freescale.com>
Subject: Re: [PATCH 1/1][v2] IFC: Change IO accessor based on endianness
Date: Thu, 13 Nov 2014 00:18:03 -0600 [thread overview]
Message-ID: <1415859483.15957.49.camel@freescale.com> (raw)
In-Reply-To: <20141112070737.GC29070@brian-ubuntu>
On Tue, 2014-11-11 at 23:07 -0800, Brian Norris wrote:
> 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.
OK.
-Scott
prev parent reply other threads:[~2014-11-13 6:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1413785506-443-1-git-send-email-b44839@freescale.com>
2014-11-03 23:22 ` [PATCH 1/1][v2] IFC: Change IO accessor based on endianness Scott Wood
2014-11-12 7:07 ` Brian Norris
2014-11-13 6:18 ` Scott Wood [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=1415859483.15957.49.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=arnd@arndb.de \
--cc=b44839@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-mtd@lists.infradead.org \
/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