Hi Doug,

On Fri, Jun 07 2013, Doug Anderson wrote:
> diff --git a/drivers/mmc/host/dw_mmc.c b/drivers/mmc/host/dw_mmc.c
> index bc3a1bc..ab5642d 100644
> --- a/drivers/mmc/host/dw_mmc.c
> +++ b/drivers/mmc/host/dw_mmc.c
> @@ -1895,7 +1895,7 @@ static int dw_mci_init_slot(struct dw_mci *host, 
> unsigned int id)
>       struct mmc_host *mmc;
>       struct dw_mci_slot *slot;
>       const struct dw_mci_drv_data *drv_data = host->drv_data;
> -     int ctrl_id, ret;
> +     int ctrl_id;
>       u8 bus_width;
>  
>       mmc = mmc_alloc_host(sizeof(struct dw_mci_slot), host->dev);
> @@ -1985,19 +1985,6 @@ static int dw_mci_init_slot(struct dw_mci *host, 
> unsigned int id)
>  #endif /* CONFIG_MMC_DW_IDMAC */
>       }
>  
> -     host->vmmc = devm_regulator_get(mmc_dev(mmc), "vmmc");
> -     if (IS_ERR(host->vmmc)) {
> -             pr_info("%s: no vmmc regulator found\n", mmc_hostname(mmc));
> -             host->vmmc = NULL;
> -     } else {
> -             ret = regulator_enable(host->vmmc);
> -             if (ret) {
> -                     dev_err(host->dev,
> -                             "failed to enable regulator: %d\n", ret);
> -                     goto err_setup_bus;
> -             }
> -     }
> -
>       if (dw_mci_get_cd(mmc))
>               set_bit(DW_MMC_CARD_PRESENT, &slot->flags);
>       else
> @@ -2023,10 +2010,6 @@ static int dw_mci_init_slot(struct dw_mci *host, 
> unsigned int id)
>       queue_work(host->card_workqueue, &host->card_work);
>  
>       return 0;
> -
> -err_setup_bus:
> -     mmc_free_host(mmc);
> -     return -EINVAL;
>  }
>  
>  static void dw_mci_cleanup_slot(struct dw_mci_slot *slot, unsigned int id)

This hunk breaks the build for me, because err_setup_bus and ret are
used in the error path of the call to mmc_add_host() in this function.

I'll push a version that leaves those in.  Let me know if you think
something strange is happening that made this work okay for you, like
a mismerge.

- Chris.
-- 
Chris Ball   <c...@laptop.org>   <http://printf.net/>
One Laptop Per Child
_______________________________________________
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss

Reply via email to