linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: eric.y.miao@gmail.com (Eric Miao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 05/10] [ARM] pxa: fix the cpu_is_pxa950
Date: Wed, 5 May 2010 14:10:40 +0800	[thread overview]
Message-ID: <p2kf17812d71005042310s59667734r57cc208849b62ef8@mail.gmail.com> (raw)
In-Reply-To: <x2q771cded01004290118tc3639f59ga7b8760de91e911f@mail.gmail.com>

On Thu, Apr 29, 2010 at 4:18 PM, Haojian Zhuang
<haojian.zhuang@gmail.com> wrote:
> From a4529b7e7e8b33d52106da10f04219d9e9b4f690 Mon Sep 17 00:00:00 2001
> From: Haojian Zhuang <haojian.zhuang@marvell.com>
> Date: Fri, 12 Mar 2010 08:51:54 -0500
> Subject: [PATCH] [ARM] pxa: fix the cpu_is_pxa950
>
> Fix the wrong variable used in cpu_is_pxa950().
>
> Signed-off-by: Haojian Zhuang <haojian.zhuang@marvell.com>

Applied.

> ---
> ?arch/arm/mach-pxa/include/mach/hardware.h | ? ?2 +-
> ?1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-pxa/include/mach/hardware.h
> b/arch/arm/mach-pxa/include/mach/hardware.h
> index 7515757..3d8d8cb 100644
> --- a/arch/arm/mach-pxa/include/mach/hardware.h
> +++ b/arch/arm/mach-pxa/include/mach/hardware.h
> @@ -202,7 +202,7 @@
> ?#define __cpu_is_pxa950(id) ? ? ? ? ? ? ? ? ? ? ? ? ? ? \
> ? ? ? ?({ ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?\
> ? ? ? ? ? ? ? ?unsigned int _id = (id) >> 4 & 0xfff; ? \
> - ? ? ? ? ? ? ? id == 0x697; ? ? ? ? ? ? ? ? ? ? ? ? ? ?\
> + ? ? ? ? ? ? ? _id == 0x697; ? ? ? ? ? ? ? ? ? ? ? ? ? \
> ? ? ? ? })
> ?#else
> ?#define __cpu_is_pxa950(id) ? ?(0)
> --
> 1.5.6.5
>

      reply	other threads:[~2010-05-05  6:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29  8:18 [PATCH 05/10] [ARM] pxa: fix the cpu_is_pxa950 Haojian Zhuang
2010-05-05  6:10 ` Eric Miao [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=p2kf17812d71005042310s59667734r57cc208849b62ef8@mail.gmail.com \
    --to=eric.y.miao@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).