From: Tony Lindgren <tony@atomide.com>
To: francisco.alecrim@indt.org.br
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] OMAP: Fix the BYTEBLOCK capability removal
Date: Thu, 15 Nov 2007 13:20:20 -0800 [thread overview]
Message-ID: <20071115212019.GL20686@atomide.com> (raw)
In-Reply-To: <1194274461-6712-1-git-send-email-francisco.alecrim@indt.org.br>
* 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
prev parent reply other threads:[~2007-11-15 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 14:54 [PATCH] OMAP: Fix the BYTEBLOCK capability removal francisco.alecrim
2007-11-15 21:20 ` Tony Lindgren [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071115212019.GL20686@atomide.com \
--to=tony@atomide.com \
--cc=francisco.alecrim@indt.org.br \
--cc=linux-omap-open-source@linux.omap.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.