All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Anderson Briglia <anderson.briglia@indt.org.br>
Cc: "Linux-omap-open-source@linux.omap.com"
	<linux-omap-open-source@linux.omap.com>,
	Russell King <rmk+lkml@arm.linux.org.uk>,
	Tony Lindgren <tony@atomide.com>,
	"Aguiar Carlos (EXT-INdT/Manaus)" <carlos.aguiar@indt.org.br>,
	ext David Brownell <david-b@pacbell.net>,
	"Lizardo Anderson (EXT-INdT/Manaus)"
	<anderson.lizardo@indt.org.br>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 1/5] [RFC] Add MMC Password Protection (lock/unlock) support V7: mmc_ignore_locked.diff
Date: Sat, 25 Nov 2006 09:39:04 +0100	[thread overview]
Message-ID: <45680128.5000506@drzeus.cx> (raw)
In-Reply-To: <45646330.9010402@indt.org.br>

Anderson Briglia wrote:
> When a card is locked, only commands from the "basic" and "lock card"
> classes
> are accepted. To be able to use the other commands, the card must be
> unlocked
> first.
>
> This patch prevents the device drivers from trying to run privileged
> class
> commands on locked MMC cards, which will fail anyway.
>

You still need to change the commit message, but otherwise the patch
looks ok.

Rgds

-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

      reply	other threads:[~2006-11-25  8:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22 14:48 [patch 1/5] [RFC] Add MMC Password Protection (lock/unlock) support V7: mmc_ignore_locked.diff Anderson Briglia
2006-11-25  8:39 ` Pierre Ossman [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=45680128.5000506@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=anderson.briglia@indt.org.br \
    --cc=anderson.lizardo@indt.org.br \
    --cc=carlos.aguiar@indt.org.br \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=rmk+lkml@arm.linux.org.uk \
    --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 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.