From: Kevin Hilman <khilman@deeprootsystems.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: linux-omap@vger.kernel.org, tony@atomide.com, b-cousson@ti.com,
Paul Walmsley <paul@pwsan.com>, Charulatha V <charu@ti.com>,
Shubhrajyoti D <shubhrajyoti@ti.com>
Subject: Re: [PATCH] OMAP: omap_device: Fix to support multiple hwmods for a single device
Date: Wed, 25 Aug 2010 11:24:00 -0700 [thread overview]
Message-ID: <87mxsaft4v.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1282732403-32227-1-git-send-email-kishon@ti.com> (Kishon Vijay Abraham, I's message of "Wed, 25 Aug 2010 16:03:23 +0530")
Kishon Vijay Abraham I <kishon@ti.com> writes:
> Currently there is a bug in the existing omap_device core code when
> extracting the hwmod structures passed to omap_device_build_ss(). This bug
> gets exposed only when passing multiple hwmod structures to
> omap_device_build_ss() resulting in incorrect extraction from second hwmod
> structure.
>
> This fix uses the pointer to pointer to omap_hwmod structure (array of
> pointers to omap_hwmod structure) passed to omap_device_build_ss() to
> correctly extract the appropriate omap_hwmod structure.
>
> This patch has been created and tested on lo/master and mainline.
>
> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
>
> Cc: Paul Walmsley<paul@pwsan.com>
> Cc: Benoit Cousson<b-cousson@ti.com>
> Cc: Kevin Hilman<khilman@deeprootsystems.com>
> Cc: Charulatha V<charu@ti.com>
> Cc: Shubhrajyoti D<shubhrajyoti@ti.com>
Acked-by: Kevin Hilman <khilman@deeprootsystems.com>
prev parent reply other threads:[~2010-08-25 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 10:33 [PATCH] OMAP: omap_device: Fix to support multiple hwmods for a single device Kishon Vijay Abraham I
2010-08-25 18:24 ` Kevin Hilman [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=87mxsaft4v.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=b-cousson@ti.com \
--cc=charu@ti.com \
--cc=kishon@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=shubhrajyoti@ti.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.