[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090402175148.GA29544@pengutronix.de>
Date: Thu, 2 Apr 2009 19:51:48 +0200
From: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
To: linux-kernel@...r.kernel.org
Cc: Grazvydas Ignotas <notasas@...il.com>,
Pierre Ossman <drzeus-mmc@...eus.cx>,
David Brownell <dbrownell@...rs.sourceforge.net>,
Tony Lindgren <tony@...mide.com>,
Russell King <rmk+kernel@....linux.org.uk>,
Paul Walmsley <paul@...an.com>,
Jarkko Lavinen <jarkko.lavinen@...ia.com>,
Hiroshi DOYU <Hiroshi.DOYU@...ia.com>,
Kyungmin Park <kyungmin.park@...sung.com>,
Carlos Eduardo Aguiar <carlos.aguiar@...t.org.br>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] make mmci-omap using platform_driver_probe
Hello,
Ups, sorry, I got the In-Reply-To wrong. This should have been a reply
to <1238196439-16535-27-git-send-email-u.kleine-koenig@...gutronix.de>.
Best regards
Uwe
On Thu, Apr 02, 2009 at 07:47:41PM +0200, Uwe Kleine-König wrote:
> A pointer to mmc_omap_probe which lives in .init.text is passed to the
> core via platform_driver_register and so the kernel might oops if probe
> is called after the init code is discarded.
>
> As requested by David Brownell platform_driver_probe is used instead of
> moving the probe function to .devinit.text. This saves some memory, but
> might have the downside that a device being registered after the call to
> mmc_omap_init but before the init sections are discarded will not be
> bound anymore to the driver.
--
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists