From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Anderson Briglia <anderson.briglia@indt.org.br>
Cc: "Linux-omap-open-source@linux.omap.com"
<linux-omap-open-source@linux.omap.com>,
linux-kernel@vger.kernel.org,
Pierre Ossman <drzeus-list@drzeus.cx>,
ext David Brownell <david-b@pacbell.net>,
Tony Lindgren <tony@atomide.com>,
"Aguiar Carlos (EXT-INdT/Manaus)" <carlos.aguiar@indt.org.br>,
"Biris Ilias (EXT-INdT/Manaus)" <Ilias.Biris@indt.org.br>
Subject: Re: [patch 3/6] [RFC] Add MMC Password Protection (lock/unlock) support V6
Date: Fri, 17 Nov 2006 16:08:55 +0000 [thread overview]
Message-ID: <20061117160855.GC28514@flint.arm.linux.org.uk> (raw)
In-Reply-To: <455DB31C.40907@indt.org.br>
On Fri, Nov 17, 2006 at 09:03:24AM -0400, Anderson Briglia wrote:
> @@ -101,7 +104,7 @@ mmc_start_request(struct mmc_host *host,
> pr_debug("%s: starting CMD%u arg %08x flags %08x\n",
> mmc_hostname(host), mrq->cmd->opcode,
> mrq->cmd->arg, mrq->cmd->flags);
> -
> +
Random whitespace damage; please remove.
> + do {
> + /* we cannot use "retries" here because the
> + * R1_LOCK_UNLOCK_FAILED bit is cleared by subsequent reads
> to
#include <std-mail-wrapping-complaint.h>
> +error:
> + mmc_deselect_cards(card->host);
You don't need to deselect the card prior to releasing the host; in
fact in single card systems, it's better that you don't. That way
you avoid generating lots of select card messages.
> + mmc_card_release_host(card);
> +out:
> + kfree(data_buf);
> +
> + return err;
> +}
> +
> +//EXPORT_SYMBOL(mmc_lock_unlock);
Either export it or don't. There's no point in having a commented out
export.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
prev parent reply other threads:[~2006-11-17 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 13:03 [patch 3/6] [RFC] Add MMC Password Protection (lock/unlock) support V6 Anderson Briglia
2006-11-17 16:08 ` Russell King [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=20061117160855.GC28514@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=Ilias.Biris@indt.org.br \
--cc=anderson.briglia@indt.org.br \
--cc=carlos.aguiar@indt.org.br \
--cc=david-b@pacbell.net \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap-open-source@linux.omap.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).