public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Bharat Bhushan <r65777@rhuath.am.freescale.net>
Cc: gregkh@linuxfoundation.org, linux-mtd@lists.infradead.org,
	prabhakar@freescale.com, arnd@arndb.de,
	Jaiprakash Singh <b44839@freescale.com>
Subject: Re: [PATCH 1/1] [RESEND] IFC: Change IO accessor based on endianness
Date: Tue, 12 May 2015 08:55:51 -0500	[thread overview]
Message-ID: <1431438951.16357.490.camel@freescale.com> (raw)
In-Reply-To: <1431420591-20453-1-git-send-email-r65777@rhuath.am.freescale.net>

On Tue, 2015-05-12 at 03:49 -0500, Bharat Bhushan 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>
> ---
>  Tested on T1040RDB, LS2085a, LS1
> 
>  .../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(-)

As before,
Acked-by: Scott Wood <scottwood@freescale.com>

This touches MTD as well as dependencies outside MTD -- which tree
should it go through?

-Scott

       reply	other threads:[~2015-05-12 13:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1431420591-20453-1-git-send-email-r65777@rhuath.am.freescale.net>
2015-05-12 13:55 ` Scott Wood [this message]
2015-05-19 22:01   ` [PATCH 1/1] [RESEND] IFC: Change IO accessor based on endianness Brian Norris
2015-05-21  1:49     ` Scott Wood
2015-05-21  2:00       ` Brian Norris
2015-05-21  2:01       ` Scott Wood
2015-05-21  2:04         ` Brian Norris
2015-05-21  2:14           ` Scott Wood
2015-05-21  2:19             ` 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=1431438951.16357.490.camel@freescale.com \
    --to=scottwood@freescale.com \
    --cc=arnd@arndb.de \
    --cc=b44839@freescale.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=prabhakar@freescale.com \
    --cc=r65777@rhuath.am.freescale.net \
    /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