public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: cpu_is_omap15xx() doesn't get set for OMAP310
Date: Thu, 4 Sep 2008 23:10:27 +0100	[thread overview]
Message-ID: <20080904221027.GI2309@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20080904215109.GV23085@atomide.com>

On Thu, Sep 04, 2008 at 02:51:13PM -0700, Tony Lindgren wrote:
> The ugly short term fix would be to define IS_OMAP_CLASS in a different
> way for omap1 and omap2. Anyways, I can fix it properly unless you're
> already patching it.

Haven't pushed any fix for it; my temporary workaround for it was quite
hacky to the extent of breaking omap2.

  reply	other threads:[~2008-09-04 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-04 21:10 cpu_is_omap15xx() doesn't get set for OMAP310 Russell King - ARM Linux
2008-09-04 21:51 ` Tony Lindgren
2008-09-04 22:10   ` Russell King - ARM Linux [this message]
2008-09-10  3:38     ` 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=20080904221027.GI2309@flint.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox