From: Scott Wood <scottwood@freescale.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: <linux-mtd@lists.infradead.org>, <linuxppc-dev@lists.ozlabs.org>,
Jaiprakash Singh <b44839@freescale.com>
Subject: Re: [v5,RESEND] IFC: Change IO accessor based on endianness
Date: Tue, 4 Aug 2015 15:37:03 -0500 [thread overview]
Message-ID: <1438720623.2097.95.camel@freescale.com> (raw)
In-Reply-To: <20150528011910.GA16716@home.buserror.net>
On Wed, 2015-05-27 at 20:19 -0500, Scott Wood wrote:
> On Wed, May 20, 2015 at 09:17:11PM -0500, Scott Wood wrote:
> > From: Jaiprakash Singh <b44839@freescale.com>
> >
> > 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>
> > Signed-off-by: Scott Wood <scottwood@freescale.com>
> > ---
> > v5: I'm assuming it's the same as v4, but I didn't send v4, and this
> > comes from a versionless [RESEND] that never made it to the mailing list,
> > so bumping the version just in case.
> >
> > .../bindings/memory-controllers/fsl/ifc.txt | 3 +
> > drivers/memory/fsl_ifc.c | 43 ++--
> > drivers/mtd/nand/fsl_ifc_nand.c | 258 +++++++++++-----
> > -----
> > include/linux/fsl_ifc.h | 50 ++++
> > 4 files changed, 213 insertions(+), 141 deletions(-)
>
> Brian, can I get an ack for this?
ping
-Scott
next prev parent reply other threads:[~2015-08-04 20:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 2:17 [PATCH v5 RESEND] IFC: Change IO accessor based on endianness Scott Wood
2015-05-21 2:17 ` Scott Wood
2015-05-28 1:19 ` [v5,RESEND] " Scott Wood
2015-05-28 1:19 ` Scott Wood
2015-08-04 20:37 ` Scott Wood [this message]
2015-08-06 16:52 ` [PATCH v5 RESEND] " Brian Norris
2015-08-06 23:24 ` Scott Wood
2015-08-06 23:44 ` Brian Norris
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=1438720623.2097.95.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=b44839@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.