The patch titled spi-imx: don't access struct device directly but use dev_get_platdata has been removed from the -mm tree. Its filename was spi-imx-dont-access-struct-device-directly-but-use-dev_get_platdata.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: spi-imx: don't access struct device directly but use dev_get_platdata From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx> Also there is no casting needed to assign a void pointer. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx> Cc: David Brownell <dbrownell@xxxxxxxxxxxxxxxxxxxxx> Cc: Daniel Mack <daniel@xxxxxxxx> Cc: Sascha Hauer <s.hauer@xxxxxxxxxxxxxx> Cc: Grant Likely <grant.likely@xxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/spi/spi_imx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN drivers/spi/spi_imx.c~spi-imx-dont-access-struct-device-directly-but-use-dev_get_platdata drivers/spi/spi_imx.c --- a/drivers/spi/spi_imx.c~spi-imx-dont-access-struct-device-directly-but-use-dev_get_platdata +++ a/drivers/spi/spi_imx.c @@ -492,7 +492,7 @@ static int __init spi_imx_probe(struct p struct resource *res; int i, ret; - mxc_platform_info = (struct spi_imx_master *)pdev->dev.platform_data; + mxc_platform_info = dev_get_platdata(&pdev->dev); if (!mxc_platform_info) { dev_err(&pdev->dev, "can't get the platform data\n"); return -EINVAL; _ Patches currently in -mm which might be from u.kleine-koenig@xxxxxxxxxxxxxx are origin.patch linux-next.patch hrtimer-correct-a-few-numbers-in-comments.patch clockevents-ensure-taht-min_delta_ns-is-increased-in-error-path.patch mxcmmc-fix-error-path-in-mxcmci_probe.patch spi-imx-use-platform_driver_probe-as-probe-lives-in-inittext.patch rtc-add-freescale-mc13783-rtc-driver.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html