diff options
Diffstat (limited to 'target/linux/brcm2708/patches-4.19/950-0392-bcm2835-mmc-Deduplicate-reset-of-driver-data-on-remo.patch')
| -rw-r--r-- | target/linux/brcm2708/patches-4.19/950-0392-bcm2835-mmc-Deduplicate-reset-of-driver-data-on-remo.patch | 26 |
1 files changed, 26 insertions, 0 deletions
diff --git a/target/linux/brcm2708/patches-4.19/950-0392-bcm2835-mmc-Deduplicate-reset-of-driver-data-on-remo.patch b/target/linux/brcm2708/patches-4.19/950-0392-bcm2835-mmc-Deduplicate-reset-of-driver-data-on-remo.patch new file mode 100644 index 0000000000..2e897aedc0 --- /dev/null +++ b/target/linux/brcm2708/patches-4.19/950-0392-bcm2835-mmc-Deduplicate-reset-of-driver-data-on-remo.patch @@ -0,0 +1,26 @@ +From 706fb772745fae3b0ea6a36830cc92eaf1c22606 Mon Sep 17 00:00:00 2001 +From: Lukas Wunner <lukas@wunner.de> +Date: Sat, 19 Jan 2019 08:42:40 +0100 +Subject: [PATCH 392/703] bcm2835-mmc: Deduplicate reset of driver data on + remove + +The BCM2835 MMC host driver sets the device's driver data pointer to +NULL on ->remove() even though the driver core subsequently does the +same in __device_release_driver(). Drop the duplicate assignment. + +Signed-off-by: Lukas Wunner <lukas@wunner.de> +Cc: Frank Pavlic <f.pavlic@kunbus.de> +--- + drivers/mmc/host/bcm2835-mmc.c | 1 - + 1 file changed, 1 deletion(-) + +--- a/drivers/mmc/host/bcm2835-mmc.c ++++ b/drivers/mmc/host/bcm2835-mmc.c +@@ -1561,7 +1561,6 @@ static int bcm2835_mmc_remove(struct pla + dma_release_channel(host->dma_chan_rxtx); + + mmc_free_host(host->mmc); +- platform_set_drvdata(pdev, NULL); + + return 0; + } |