Re: [GIT PULL] omap fixes for v2.6.32-rc3

From: Uwe Kleine-König
Date: Fri Oct 09 2009 - 04:33:06 EST


Hello,

On Fri, Oct 09, 2009 at 11:25:47AM +0300, Felipe Contreras wrote:
> 2009/10/9 Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>:
> > Hello,
> >
> > On Fri, Oct 09, 2009 at 01:13:01AM +0300, Felipe Contreras wrote:
> >> On Fri, Oct 9, 2009 at 12:41 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote:
> >> > * Felipe Contreras <felipe.contreras@xxxxxxxxx> [091008 14:29]:
> >> >> On Wed, Oct 7, 2009 at 9:51 PM, Tony Lindgren <tony@xxxxxxxxxxx> 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.
> >>
> >> Should it?
> >>
> >> Here you can see Uwe Kleine-König sending the original patch without
> >> even CC'ing the mmc list:
> >> http://marc.info/?l=linux-kernel&m=124820861213849&w=2
> > Note these are different patches.  Mine fixes a section problem as the
> > probe function used to live in .init.text but was still used with
> > platform_driver_register.
>
> Maybe you looked at the wrong diff. This is the patch that is going to
> be pushed eventually:
> http://marc.info/?l=linux-mmc&m=125504287632070&w=2
>
> As you can see it's restoring back what you intended in the original patch.
Yes, but back then it was broken in a different way. Now the driver's
probe function hasn't been called at all. My fix addressed a possible
oops because it could be called when is was already discarded.

Best regards
Uwe

--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/