From: Paul Walmsley <paul@pwsan.com>
To: Tero Kristo <tero.kristo@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCHv4 6/8] OMAP3: Clock: Added IDLEST definitions for SGX
Date: Mon, 1 Feb 2010 15:02:00 -0700 (MST) [thread overview]
Message-ID: <alpine.DEB.2.00.1002011501401.20004@utopia.booyaka.com> (raw)
In-Reply-To: <1264182951-9205-7-git-send-email-tero.kristo@nokia.com>
On Fri, 22 Jan 2010, Tero Kristo wrote:
> From: Tero Kristo <tero.kristo@nokia.com>
>
> Added definitions for OMAP3430ES2_ST_SGX_SHIFT and OMAP3430ES2_ST_SGX_MASK
> as these were missing.
>
> Signed-off-by: Tero Kristo <tero.kristo@nokia.com>
Thanks Tero, queued for 2.6.34.
- Paul
next prev parent reply other threads:[~2010-02-01 22:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 17:55 [PATCHv4 0/8] Idle status patches revisited Tero Kristo
2010-01-22 17:55 ` [PATCHv4 1/8] OMAP3: Clockdomain: Added API for checking if HWSUP is enabled Tero Kristo
2010-01-22 17:55 ` [PATCHv4 2/8] OMAP: Powerdomains: Add support for INACTIVE state on pwrdm level Tero Kristo
2010-01-22 17:55 ` [PATCHv4 3/8] OMAP3: PM: Added support for INACTIVE and ON states for powerdomains Tero Kristo
2010-01-22 17:55 ` [PATCHv4 4/8] OMAP3: CPUidle: Fixed support for ON / INACTIVE states Tero Kristo
2010-01-22 17:55 ` [PATCHv4 5/8] OMAP3: PM: Removed pwrdm state hacking from omap_sram_idle Tero Kristo
2010-01-22 17:55 ` [PATCHv4 6/8] OMAP3: Clock: Added IDLEST definitions for SGX Tero Kristo
2010-01-22 17:55 ` [PATCHv4 7/8] OMAP: Powerdomains: Add support for checking if pwrdm/clkdm can idle Tero Kristo
2010-01-22 17:55 ` [PATCHv4 8/8] OMAP3: CPUidle: Added peripheral pwrdm checks into bm check Tero Kristo
2010-02-01 22:02 ` Paul Walmsley [this message]
2010-02-02 8:03 ` [PATCHv4 2/8] OMAP: Powerdomains: Add support for INACTIVE state on pwrdm level Paul Walmsley
2010-02-02 9:26 ` Tero.Kristo
2010-02-01 22:10 ` [PATCHv4 1/8] OMAP3: Clockdomain: Added API for checking if HWSUP is enabled Paul Walmsley
2010-02-02 8:39 ` Tero.Kristo
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=alpine.DEB.2.00.1002011501401.20004@utopia.booyaka.com \
--to=paul@pwsan.com \
--cc=linux-omap@vger.kernel.org \
--cc=tero.kristo@nokia.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.