* [PATCH] OMAP: Fix the BYTEBLOCK capability removal
@ 2007-11-05 14:54 francisco.alecrim
2007-11-15 21:20 ` Tony Lindgren
0 siblings, 1 reply; 2+ messages in thread
From: francisco.alecrim @ 2007-11-05 14:54 UTC (permalink / raw)
To: linux-omap-open-source
From: Francisco Alecrim <francisco.alecrim@indt.org.br>
According with commit 255d01af9a990fd5166f04ed0cc0b30b7b67e81e
from Linux-OMAP tree, the BYTEBLOCK capability was removed by Pierre Ossman.
MMC_CAP_BYTEBLOCK is not defined causing the compile error:
drivers/mmc/host/omap.c: In function `mmc_omap_probe':
drivers/mmc/host/omap.c:1077: error: `MMC_CAP_BYTEBLOCK' undeclared (first use in this function)
drivers/mmc/host/omap.c:1077: error: (Each undeclared identifier is reported only once
drivers/mmc/host/omap.c:1077: error: for each function it appears in.)
Signed-off-by: Francisco Alecrim <francisco.alecrim@indt.org.br>
Signed-off-by: Carlos Eduardo Aguiar <carlos.aguiar@indt.org.br>
---
drivers/mmc/host/omap.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/mmc/host/omap.c b/drivers/mmc/host/omap.c
index 87dc63a..ea8dbde 100644
--- a/drivers/mmc/host/omap.c
+++ b/drivers/mmc/host/omap.c
@@ -1074,7 +1074,7 @@ static int __init mmc_omap_probe(struct platform_device *pdev)
mmc->f_min = 400000;
mmc->f_max = 24000000;
mmc->ocr_avail = MMC_VDD_32_33 | MMC_VDD_33_34;
- mmc->caps = MMC_CAP_MULTIWRITE | MMC_CAP_BYTEBLOCK;
+ mmc->caps = MMC_CAP_MULTIWRITE;
if (minfo->wire4)
mmc->caps |= MMC_CAP_4_BIT_DATA;
--
1.5.3.4.395.g85b0
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] OMAP: Fix the BYTEBLOCK capability removal
2007-11-05 14:54 [PATCH] OMAP: Fix the BYTEBLOCK capability removal francisco.alecrim
@ 2007-11-15 21:20 ` Tony Lindgren
0 siblings, 0 replies; 2+ messages in thread
From: Tony Lindgren @ 2007-11-15 21:20 UTC (permalink / raw)
To: francisco.alecrim; +Cc: linux-omap-open-source
* francisco.alecrim@indt.org.br <francisco.alecrim@indt.org.br> [071105 06:51]:
> From: Francisco Alecrim <francisco.alecrim@indt.org.br>
>
> According with commit 255d01af9a990fd5166f04ed0cc0b30b7b67e81e
> from Linux-OMAP tree, the BYTEBLOCK capability was removed by Pierre Ossman.
> MMC_CAP_BYTEBLOCK is not defined causing the compile error:
>
> drivers/mmc/host/omap.c: In function `mmc_omap_probe':
> drivers/mmc/host/omap.c:1077: error: `MMC_CAP_BYTEBLOCK' undeclared (first use in this function)
> drivers/mmc/host/omap.c:1077: error: (Each undeclared identifier is reported only once
> drivers/mmc/host/omap.c:1077: error: for each function it appears in.)
>
> Signed-off-by: Francisco Alecrim <francisco.alecrim@indt.org.br>
> Signed-off-by: Carlos Eduardo Aguiar <carlos.aguiar@indt.org.br>
> ---
> drivers/mmc/host/omap.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mmc/host/omap.c b/drivers/mmc/host/omap.c
> index 87dc63a..ea8dbde 100644
> --- a/drivers/mmc/host/omap.c
> +++ b/drivers/mmc/host/omap.c
> @@ -1074,7 +1074,7 @@ static int __init mmc_omap_probe(struct platform_device *pdev)
> mmc->f_min = 400000;
> mmc->f_max = 24000000;
> mmc->ocr_avail = MMC_VDD_32_33 | MMC_VDD_33_34;
> - mmc->caps = MMC_CAP_MULTIWRITE | MMC_CAP_BYTEBLOCK;
> + mmc->caps = MMC_CAP_MULTIWRITE;
>
> if (minfo->wire4)
> mmc->caps |= MMC_CAP_4_BIT_DATA;
> --
Pushing today.
Tony
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-11-15 21:20 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-05 14:54 [PATCH] OMAP: Fix the BYTEBLOCK capability removal francisco.alecrim
2007-11-15 21:20 ` Tony Lindgren
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox