public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] NAND: DaVinci: Adding 4 BIT ECC support
Date: Tue, 18 Aug 2009 10:28:43 -0500	[thread overview]
Message-ID: <4A8AC8AB.5020000@freescale.com> (raw)
In-Reply-To: <0554BEF07D437848AF01B9C9B5F0BC5D7E99635F@dlee01.ent.ti.com>

Paulraj, Sandeep wrote:
>> What I mean is using accessors such as readl/writel -- though we're still
>> in a pretty sorry state with respect to what accessors we provide cross
>> architectures (you have to pick between native endian with no barriers,
>> or little endian with barriers).
> 
> Scott, I am quite certain that I have received comments for other
> patches that I have submitted earlier where I have been specifically
> been asked to do things the way I am doing at the moment and not use
> readl/writel(because of the reason you mentioned above).

OK, I didn't see those comments.

> So should I assume that my updated patch has your ACK as you mentioned above that you want NACK it

It looks OK.

-Scott

  reply	other threads:[~2009-08-18 15:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 14:45 [U-Boot] [PATCH] NAND: DaVinci: Adding 4 BIT ECC support s-paulraj at ti.com
2009-08-17 22:03 ` Jean-Christophe PLAGNIOL-VILLARD
2009-08-17 22:34   ` Wolfgang Denk
2009-08-18  0:03   ` Scott Wood
2009-08-18  0:03 ` Scott Wood
2009-08-18 13:56   ` Paulraj, Sandeep
2009-08-18 15:12     ` Scott Wood
2009-08-18 15:21       ` Paulraj, Sandeep
2009-08-18 15:28         ` Scott Wood [this message]
     [not found]           ` <0554BEF07D437848AF01B9C9B5F0BC5D7E9963C1@dlee01.ent.ti.com>
2009-08-18 15:42             ` Scott Wood
2009-08-18 19:28               ` Wolfgang Denk
2009-08-18 19:53                 ` Paulraj, Sandeep
2009-08-18 19:26         ` Wolfgang Denk
2009-08-18 19:24       ` Wolfgang Denk

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=4A8AC8AB.5020000@freescale.com \
    --to=scottwood@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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