Fix a common error in nand-drivers which do not set up a parent device for the mtd-device by using a new inline function.
Signed-off-by: Alexander Holler <hol...@ahsoftware.de> --- drivers/mtd/nand/omap2.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c index 1ff49b8..c761334 100644 --- a/drivers/mtd/nand/omap2.c +++ b/drivers/mtd/nand/omap2.c @@ -1598,9 +1598,8 @@ static int omap_nand_probe(struct platform_device *pdev) info->of_node = pdata->of_node; info->ecc_opt = pdata->ecc_opt; mtd = &info->mtd; - mtd->priv = &info->nand; + mtd_setup_common_members(mtd, &info->nand, pdev); mtd->name = dev_name(&pdev->dev); - mtd->owner = THIS_MODULE; nand_chip = &info->nand; nand_chip->ecc.priv = NULL; nand_chip->options |= NAND_SKIP_BBTSCAN; -- 1.8.3.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/