linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap fixes for v2.6.32-rc3
Date: Thu, 8 Oct 2009 14:41:41 -0700	[thread overview]
Message-ID: <20091008214140.GJ7417@atomide.com> (raw)
In-Reply-To: <94a0d4530910081429m7ad88b43q38245109f3252078@mail.gmail.com>

* Felipe Contreras <felipe.contreras@gmail.com> [091008 14:29]:
> On Wed, Oct 7, 2009 at 9:51 PM, Tony Lindgren <tony@atomide.com> wrote:
> > Linus,
> >
> > Please pull omap fixes from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git omap-fixes-for-linus
> >
> > Regards,
> >
> > Tony
> >
> >
> > The following changes since commit 374576a8b6f865022c0fd1ca62396889b23d66dd:
> > ?Linus Torvalds (1):
> > ? ? ? ?Linux 2.6.32-rc3
> >
> > are available in the git repository at:
> >
> > ?git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git omap-fixes-for-linus
> >
> > Artem Bityutskiy (1):
> > ? ? ?OMAP3: PM: introduce a new powerdomain walk helper
> >
> > Daniel Walker (1):
> > ? ? ?omap: iovmm: Add missing mutex_unlock
> >
> > Hiroshi DOYU (1):
> > ? ? ?omap: iovmm: Fix incorrect spelling
> >
> > Jon Hunter (1):
> > ? ? ?OMAP3: PM: Prevent hang in prcm_interrupt_handler
> >
> > Kevin Hilman (1):
> > ? ? ?OMAP3: PM: Enable GPIO module-level wakeups
> >
> > Paul Walmsley (2):
> > ? ? ?OMAP3: PM: PRCM interrupt: check MPUGRPSEL register
> > ? ? ?OMAP3: PM: PRCM interrupt: only handle selected PRCM interrupts
> >
> > Rajendra Nayak (1):
> > ? ? ?omap: Lock DPLL5 at boot
> >
> > Sergio Aguirre (1):
> > ? ? ?omapfb: Condition mutex acquisition
> >
> > Tommi Rantala (2):
> > ? ? ?omapfb: Blizzard: fix pointer to be const
> > ? ? ?omapfb: Blizzard: constify register address tables
> >
> > Tony Lindgren (2):
> > ? ? ?omap: Fix incorrect 730 vs 850 detection
> > ? ? ?Merge branch 'pm-fixes-32' of git://git.kernel.org/.../khilman/linux-omap-pm into omap-fixes-for-linus
> >
> > Vikram Pandita (1):
> > ? ? ?OMAP3: PM: USBHOST: clear wakeup events on both hosts
> >
> > ye janboe (1):
> > ? ? ?omap: SRAM: flush the right address after memcpy in omap_sram_push
> 
> The beagleboard is still not booting for me with this branch, I need
> to add these two patches:
> 
> * http://patchwork.kernel.org/patch/50721/
> 

This should go to the mainline kernel via Samuel as it's
drivers/mfd related.

> This one is needed because the defconfig has:
> CONFIG_TWL4030_USB=y
> 
> * http://patchwork.kernel.org/patch/50970/
> 
> This is needed because most people boot from an MMC.

And this should go in via the mmc list.

So little more patience is still needed :)

Cheers,

Tony

> 
> You can add my 'tested-by' line if you want.
> 
> Cheers.
> 
> -- 
> Felipe Contreras

  reply	other threads:[~2009-10-08 21:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-07 18:51 [GIT PULL] omap fixes for v2.6.32-rc3 Tony Lindgren
2009-10-08 21:29 ` Felipe Contreras
2009-10-08 21:41   ` Tony Lindgren [this message]
2009-10-08 22:13     ` Felipe Contreras
2009-10-08 22:20       ` Felipe Contreras
2009-10-08 23:26         ` Tony Lindgren
2009-10-09  8:02       ` Uwe Kleine-König
2009-10-09  8:25         ` Felipe Contreras
2009-10-09  8:30           ` Uwe Kleine-König

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=20091008214140.GJ7417@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).