public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] OMAP: hwmod/device/CM: bug fixes for 2.6.37
Date: Fri, 24 Sep 2010 10:40:11 -0600	[thread overview]
Message-ID: <20100924163936.19418.47065.stgit@twilight.localdomain> (raw)

Hello,

Here are a few bugfix patches for the omap_hwmod, omap_device,
and CM code, intended to be merged in 2.6.37 via Tony's tree.
 
This series applies on top of the 2.6.37 hwmod patches sent earlier;
unfortunately the third patch touches the same code as a patch in that
series, so this series can't be based on v2.6.36-rc5.


- Paul

---

   text	   data	    bss	    dec	    hex	filename
3361500	 176832	  99336	3637668	 3781a4	vmlinux.omap_4430sdp_defconfig.orig
3361468	 176832	  99336	3637636	 378184	vmlinux.omap_4430sdp_defconfig.patched

Hema HK (1):
      OMAP: hwmod: Set autoidle after smartidle during _sysc_enable

Kishon Vijay Abraham I (1):
      OMAP: omap_device: Fix to support multiple hwmods for a single device

Rajendra Nayak (1):
      OMAP4: PM: Declare idle modules as functional too


 arch/arm/mach-omap2/cm4xxx.c     |    9 +++++----
 arch/arm/mach-omap2/omap_hwmod.c |   17 +++++++++++------
 arch/arm/plat-omap/omap_device.c |   35 ++++++++++++++---------------------
 3 files changed, 30 insertions(+), 31 deletions(-)


             reply	other threads:[~2010-09-24 16:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24 16:40 Paul Walmsley [this message]
2010-09-24 16:40 ` [PATCH 1/3] OMAP: omap_device: Fix to support multiple hwmods for a single device Paul Walmsley
2010-09-24 16:40 ` [PATCH 2/3] OMAP4: PM: Declare idle modules as functional too Paul Walmsley
2010-09-24 16:40 ` [PATCH 3/3] OMAP: hwmod: Set autoidle after smartidle during _sysc_enable 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=20100924163936.19418.47065.stgit@twilight.localdomain \
    --to=paul@pwsan.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    /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