[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <457483B5.8060205@drzeus.cx>
Date: Mon, 04 Dec 2006 21:23:17 +0100
From: Pierre Ossman <drzeus-list@...eus.cx>
To: Anderson Briglia <anderson.briglia@...t.org.br>
CC: "Linux-omap-open-source@...ux.omap.com"
<linux-omap-open-source@...ux.omap.com>,
Russell King <rmk+lkml@....linux.org.uk>,
Tony Lindgren <tony@...mide.com>,
"Aguiar Carlos (EXT-INdT/Manaus)" <carlos.aguiar@...t.org.br>,
ext David Brownell <david-b@...bell.net>,
"Lizardo Anderson (EXT-INdT/Manaus)" <anderson.lizardo@...t.org.br>,
linux-kernel@...r.kernel.org
Subject: Re: [patch 3/5] [RFC] Add MMC Password Protection (lock/unlock) support
V7: mmc_lock_unlock.diff
Anderson Briglia wrote:
>
> Actually they represent the bits regarding the modes and it is used
> when we
> have to send the LOCK/UNLOCK mode on the command data block, according
> to the MMC Spec.
> If you take a look at mmc_lock_unlock function, we use those modes to
> set the right bit
> when composing the command data block.
> This definition makes the code more legible and simple.
In that case you need to change the code to make sure it is clear that
it is bits and not values. Also, your definition for
MMC_LOCK_MODE_UNLOCK is wrong.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists