All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Carlos Aguiar <carlos.aguiar@indt.org.br>
Cc: linux-kernel@vger.kernel.org,
	linux-omap-open-source@linux.omap.com,
	David Brownell <david-b@pacbell.net>,
	Tony Lindgren <tony@atomide.com>,
	Russell King <rmk+lkml@arm.linux.org.uk>,
	ilias.biris@indt.org.br
Subject: Re: [patch 1/6] [RFC] Add MMC Password Protection (lock/unlock) support V5
Date: Sun, 29 Oct 2006 10:26:08 +0100	[thread overview]
Message-ID: <454473B0.8040901@drzeus.cx> (raw)
In-Reply-To: <20061020165131.681329000@localhost.localdomain>

Carlos Aguiar 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 block driver from trying to run privileged class
> commands on locked MMC cards, which will fail anyway.
>   

Incorrect commit message. It stops driver probes (all of them).

> 20 11:41:54.000000000 -0400
> @@ -85,6 +85,7 @@ struct mmc_host {
>  	unsigned long		caps;		/* Host capabilities */
>  
>  #define MMC_CAP_4_BIT_DATA	(1 << 0)	/* Can the host do 4 bit transfers */
> +#define MMC_CAP_LOCK_UNLOCK	(1 << 1)	/* Host password support capability */
>  
>  	/* host specific block data */
>  	unsigned int		max_seg_size;	/* see blk_queue_max_segment_size */
>
>   

You  need to rebase your patch set on a more recent kernel. This won't
apply cleanly.

Rgds

-- 
     -- Pierre Ossman

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

  parent reply	other threads:[~2006-10-29  9:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20061020164914.012378000@localhost.localdomain>
2006-10-23  6:03 ` [patch 0/6] [RFC] Add MMC Password Protection (lock/unlock) support V5 Pierre Ossman
2006-10-23 16:44   ` Russell King
     [not found] ` <20061020165131.681329000@localhost.localdomain>
2006-10-29  9:26   ` Pierre Ossman [this message]
     [not found] ` <20061020165134.378993000@localhost.localdomain>
2006-10-29  9:31   ` [patch 2/6] " Pierre Ossman
     [not found] ` <20061020165135.162482000@localhost.localdomain>
2006-10-29  9:49   ` [patch 3/6] " Pierre Ossman
2006-10-30  2:06     ` David Brownell
     [not found] ` <20061020165135.852337000@localhost.localdomain>
2006-10-29  9:52   ` [patch 4/6] " Pierre Ossman
     [not found] ` <20061020165136.664879000@localhost.localdomain>
2006-10-29  9:57   ` [patch 5/6] " Pierre Ossman
     [not found] ` <20061020165139.911232000@localhost.localdomain>
2006-10-29  9:57   ` [patch 6/6] " Pierre Ossman

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=454473B0.8040901@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=carlos.aguiar@indt.org.br \
    --cc=david-b@pacbell.net \
    --cc=ilias.biris@indt.org.br \
    --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.