All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anderson Briglia <anderson.briglia@indt.org.br>
To: Anderson Briglia <anderson.briglia@indt.org.br>,
	"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 1/6] [RFC] Add MMC Password Protection (lock/unlock) support V6
Date: Fri, 17 Nov 2006 19:04:30 -0400	[thread overview]
Message-ID: <455E3FFE.90001@indt.org.br> (raw)
In-Reply-To: <20061117160414.GA28514@flint.arm.linux.org.uk>

Hi Russel and Pierre,

Thanks for all comments, I'm fixing the series and will send another version asap.

ext Russell King wrote:
> On Fri, Nov 17, 2006 at 09:01:11AM -0400, Anderson Briglia wrote:
>> Index: linux-omap-2.6.git/drivers/mmc/mmc_sysfs.c
>> ===================================================================
>> --- linux-omap-2.6.git.orig/drivers/mmc/mmc_sysfs.c	2006-11-14 
>> 08:46:54.000000000 -0400
>> +++ linux-omap-2.6.git/drivers/mmc/mmc_sysfs.c	2006-11-14 
>> 09:06:39.000000000 -0400
>> @@ -17,6 +17,7 @@
>>
>>  #include <linux/mmc/card.h>
>>  #include <linux/mmc/host.h>
>> +#include <linux/mmc/protocol.h>
> 
> Why does this file need mmc/protocol.h?  I don't see anything added
> which would require this include.

We need this here because mmc_card_lockable function uses "CCC_LOCK_CARD" macro defined on 
linux/mmc/protocol.h

> 
>> @@ -73,10 +74,19 @@ static void mmc_release_card(struct devi
>>   * This currently matches any MMC driver to any MMC card - drivers
>>   * themselves make the decision whether to drive this card in their
>>   * probe method.  However, we force "bad" cards to fail.
>> + *
>> + * We also fail for all locked cards; drivers expect to be able to do block
>> + * I/O still on probe(), which is not possible while the card is locked.
>> + * Device probing must be triggered sometime later to make the card 
>> available
> 
> Your mailer wrapped the patch...  Also it would be nice to have this manually
> wrapped so it's viewable sanely on a standard 80 column display.
> 
>> @@ -75,12 +76,19 @@ struct mmc_card {
>>  #define mmc_card_bad(c)		((c)->state & MMC_STATE_BAD)
>>  #define mmc_card_sd(c)		((c)->state & MMC_STATE_SDCARD)
>>  #define mmc_card_readonly(c)	((c)->state & MMC_STATE_READONLY)
>> +#define mmc_card_locked(c)	((c)->state & MMC_STATE_LOCKED)
>> +#define mmc_card_clear_locked(c)	((c)->state &= ~MMC_STATE_LOCKED)
> 
> Since we separate out the "mmc_card_set_xxx" macros, please do the same
> with the "mmc_card_clear_xxx" for consistency sake.
> 

  reply	other threads:[~2006-11-17 23:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17 13:01 [patch 1/6] [RFC] Add MMC Password Protection (lock/unlock) support V6 Anderson Briglia
2006-11-17 13:01 ` Anderson Briglia
2006-11-17 16:04 ` Russell King
2006-11-17 23:04   ` Anderson Briglia [this message]
2006-11-17 16:09 ` Russell King
2006-11-17 16:41   ` 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=455E3FFE.90001@indt.org.br \
    --to=anderson.briglia@indt.org.br \
    --cc=Ilias.Biris@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 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.