linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Brian Norris <computersforpeace@gmail.com>,
	<linux-mtd@lists.infradead.org>
Cc: <linuxppc-dev@lists.ozlabs.org>, Jaiprakash Singh <b44839@freescale.com>
Subject: Re: [v5,RESEND] IFC: Change IO accessor based on endianness
Date: Wed, 27 May 2015 20:19:10 -0500	[thread overview]
Message-ID: <20150528011910.GA16716@home.buserror.net> (raw)
In-Reply-To: <1432174631-30091-1-git-send-email-scottwood@freescale.com>

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?

-Scott

  reply	other threads:[~2015-05-28  1:19 UTC|newest]

Thread overview: 6+ 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-28  1:19 ` Scott Wood [this message]
2015-08-04 20:37   ` [v5,RESEND] " Scott Wood
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=20150528011910.GA16716@home.buserror.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).