From: Kevin Hilman <khilman@deeprootsystems.com>
To: Tero.Kristo@nokia.com
Cc: tony@atomide.com, paul@pwsan.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/2] adding back some features
Date: Wed, 17 Jun 2009 07:04:01 -0700 [thread overview]
Message-ID: <877hzb0xf2.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1F18D6510CF0474A8C9500565A7E41A205456C9E23@NOK-EUMSG-02.mgdnok.nokia.com> (Tero Kristo's message of "Wed\, 17 Jun 2009 15\:56\:27 +0200")
<Tero.Kristo@nokia.com> writes:
>>>
>>> This would be better if it specifically tested for HS and EMU
>>> devices. There are at least two other omap_type() possibilities
>>> here, "TEST" and "BAD"
>>
>>Tero, can you please repost? I will hold on sending out the
>>omap-fixes for that, and refresh omap-fixes with the updated patch.
>
> I'll try to look at this tomorrow if I happen to have time, I am
> currently quite busy fixing some bugs in our code base. However, if
> you need it right now and if someone wants to re-write this to check
> against TEST and BAD, I am of course okay with that (rather simple
> fix actually.) :)
I'll fix this up and resubmit.
Kevin
next prev parent reply other threads:[~2009-06-17 14:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 22:11 [PATCH 0/2] adding back some features Kevin Hilman
2009-06-12 22:11 ` [PATCH 1/2] OMAP2/3: SoC IDs: add omap_type() for determining GP/EMU/HS Kevin Hilman
2009-06-12 22:11 ` [PATCH 2/2] OMAP3: DMA: Enable idlemodes for DMA OCP Kevin Hilman
2009-06-15 8:56 ` [APPLIED] " Tony Lindgren
2009-06-17 8:33 ` [APPLIED] [PATCH 1/2] OMAP2/3: SoC IDs: add omap_type() for determining Tony Lindgren
2009-06-15 8:00 ` [PATCH 0/2] adding back some features Tony Lindgren
2009-06-15 14:55 ` Kevin Hilman
2009-06-15 16:05 ` Kevin Hilman
2009-06-17 8:31 ` Tony Lindgren
2009-06-17 8:35 ` Paul Walmsley
2009-06-17 9:58 ` Tony Lindgren
2009-06-17 13:56 ` Tero.Kristo
2009-06-17 14:04 ` Kevin Hilman [this message]
2009-06-18 0:00 ` Kevin Hilman
2009-06-17 8:39 ` [APPLIED] " 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=877hzb0xf2.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=Tero.Kristo@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--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 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.