linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Haijun Zhang <Haijun.Zhang@freescale.com>
Cc: Zhao Chenhui <chenhui.zhao@freescale.com>,
	linux-mmc@vger.kernel.org, AFLEMING@freescale.com,
	cbouatmailru@gmail.com, cjb@laptop.org,
	linuxppc-dev@lists.ozlabs.org,
	Haijun Zhang <Haijun.Zhang@freescale.com>
Subject: Re: [PATCH 1/4] powerpc/85xx: Add support for 85xx cpu type detection
Date: Mon, 8 Jul 2013 18:43:06 -0500	[thread overview]
Message-ID: <1373326986.8183.185@snotra> (raw)
In-Reply-To: <1373249545-23928-1-git-send-email-Haijun.Zhang@freescale.com> (from Haijun.Zhang@freescale.com on Sun Jul  7 21:12:22 2013)

On 07/07/2013 09:12:22 PM, Haijun Zhang wrote:
> Add this file to help detect cpu type in runtime.
> These macros and inline routines will be more favorable for driver
> to apply errata and workaround to specified cpu type.
>=20
> Signed-off-by: Haijun Zhang <Haijun.Zhang@freescale.com>
> Signed-off-by: Zhao Chenhui <chenhui.zhao@freescale.com>
> ---
>  arch/powerpc/include/asm/mpc85xx.h | 96 =20
> ++++++++++++++++++++++++++++++++++++++
>  1 file changed, 96 insertions(+)
>  create mode 100644 arch/powerpc/include/asm/mpc85xx.h

What changed since the last time this was posted?  I don't see any of =20
the feedback addressed that I gave here:

http://patchwork.ozlabs.org/patch/144880/

-Scott=

      parent reply	other threads:[~2013-07-08 23:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08  2:12 [PATCH 1/4] powerpc/85xx: Add support for 85xx cpu type detection Haijun Zhang
2013-07-08  2:12 ` [PATCH 2/4] mmc: esdhc: workaround for dma err in the last system transaction Haijun Zhang
2013-07-08  2:12 ` [PATCH 3/4] mmc: esdhc: Add quirks to support T4240 board Haijun Zhang
2013-07-08  2:12 ` [PATCH 4/4] mmc: eSDHC: Some eSDHC host need long time to generate command interrupt Haijun Zhang
2013-07-08 23:43 ` 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=1373326986.8183.185@snotra \
    --to=scottwood@freescale.com \
    --cc=AFLEMING@freescale.com \
    --cc=Haijun.Zhang@freescale.com \
    --cc=cbouatmailru@gmail.com \
    --cc=chenhui.zhao@freescale.com \
    --cc=cjb@laptop.org \
    --cc=linux-mmc@vger.kernel.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).