From: Ilya Yanok <yanok@emcraft.com>
To: Archit Taneja <a0393947@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
grinberg@compulab.co.il, sasha_d@emcraft.com,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Archit Taneja <archit@ti.com>, Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH V2] OMAP3: hwmod_data: register dss hwmods after dss_core
Date: Thu, 12 Jan 2012 01:19:52 +0400 [thread overview]
Message-ID: <4F0DFCF8.4070008@emcraft.com> (raw)
In-Reply-To: <4EFD8C36.9000208@ti.com>
Hi Archit.
On 30.12.2011 14:02, Archit Taneja wrote:
> This looks fine, but it should be needed for other OMAP2 and OMAP4 also.
> If you could extend the patch we could test it out for the other OMAPs.
OMAP2 and OMAP4 don't need this as they have single hwmod list, so
correct ordering can be handled just by ordering list items.
Regards, Ilya.
WARNING: multiple messages have this Message-ID (diff)
From: yanok@emcraft.com (Ilya Yanok)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] OMAP3: hwmod_data: register dss hwmods after dss_core
Date: Thu, 12 Jan 2012 01:19:52 +0400 [thread overview]
Message-ID: <4F0DFCF8.4070008@emcraft.com> (raw)
In-Reply-To: <4EFD8C36.9000208@ti.com>
Hi Archit.
On 30.12.2011 14:02, Archit Taneja wrote:
> This looks fine, but it should be needed for other OMAP2 and OMAP4 also.
> If you could extend the patch we could test it out for the other OMAPs.
OMAP2 and OMAP4 don't need this as they have single hwmod list, so
correct ordering can be handled just by ordering list items.
Regards, Ilya.
next prev parent reply other threads:[~2012-01-11 21:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 14:02 [PATCH] OMAP3: hwmod_data: register dss hwmods after dss_core Ilya Yanok
2011-12-22 14:02 ` Ilya Yanok
2011-12-22 15:10 ` Igor Grinberg
2011-12-22 15:10 ` Igor Grinberg
2011-12-27 23:31 ` [PATCH V2] " Ilya Yanok
2011-12-27 23:31 ` Ilya Yanok
2011-12-30 10:02 ` Archit Taneja
2011-12-30 10:02 ` Archit Taneja
2012-01-11 21:19 ` Ilya Yanok [this message]
2012-01-11 21:19 ` Ilya Yanok
2012-01-12 9:13 ` Tomi Valkeinen
2012-01-12 9:13 ` Tomi Valkeinen
2012-01-25 21:23 ` Paul Walmsley
2012-01-25 21:23 ` Paul Walmsley
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=4F0DFCF8.4070008@emcraft.com \
--to=yanok@emcraft.com \
--cc=a0393947@ti.com \
--cc=archit@ti.com \
--cc=grinberg@compulab.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=sasha_d@emcraft.com \
--cc=tomi.valkeinen@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.