All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Afzal Mohammed <afzal@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	hvaibhav@ti.com, nsekhar@ti.com
Subject: Re: [PATCH v2 1/2] ARM: OMAP2+: id: Add am33xx SoC type detection
Date: Mon, 5 Mar 2012 15:08:13 -0800	[thread overview]
Message-ID: <20120305230812.GO12083@atomide.com> (raw)
In-Reply-To: <1329113685-7500-1-git-send-email-afzal@ti.com>

* Afzal Mohammed <afzal@ti.com> [120212 22:00]:
> Determine SoC type, i.e. whether GP or HS
> 
> Note: cpu_is_34xx() is true for am33xx also. Doing
> cpu_is_am33xx() check after cpu_is_34xx() will not
> achieve what we want due to the above reason.
> Hence cpu_is_am33xx() is done before cpu_is_34xx()

Thanks, applying into fixes-non-critical-part2.

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ARM: OMAP2+: id: Add am33xx SoC type detection
Date: Mon, 5 Mar 2012 15:08:13 -0800	[thread overview]
Message-ID: <20120305230812.GO12083@atomide.com> (raw)
In-Reply-To: <1329113685-7500-1-git-send-email-afzal@ti.com>

* Afzal Mohammed <afzal@ti.com> [120212 22:00]:
> Determine SoC type, i.e. whether GP or HS
> 
> Note: cpu_is_34xx() is true for am33xx also. Doing
> cpu_is_am33xx() check after cpu_is_34xx() will not
> achieve what we want due to the above reason.
> Hence cpu_is_am33xx() is done before cpu_is_34xx()

Thanks, applying into fixes-non-critical-part2.

Tony

  reply	other threads:[~2012-03-05 23:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  6:14 [PATCH v2 1/2] ARM: OMAP2+: id: Add am33xx SoC type detection Afzal Mohammed
2012-02-13  6:14 ` Afzal Mohammed
2012-03-05 23:08 ` Tony Lindgren [this message]
2012-03-05 23:08   ` Tony Lindgren

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=20120305230812.GO12083@atomide.com \
    --to=tony@atomide.com \
    --cc=afzal@ti.com \
    --cc=hvaibhav@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nsekhar@ti.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.