[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45A4ECDF.8090707@indt.org.br>
Date: Wed, 10 Jan 2007 09:40:47 -0400
From: Anderson Briglia <anderson.briglia@...t.org.br>
To: ext Pierre Ossman <drzeus-list@...eus.cx>
CC: Russell King <rmk+lkml@....linux.org.uk>,
"Lizardo Anderson (EXT-INdT/Manaus)" <anderson.lizardo@...t.org.br>,
linux-kernel@...r.kernel.org,
"Aguiar Carlos (EXT-INdT/Manaus)" <carlos.aguiar@...t.org.br>,
Tony Lindgren <tony@...mide.com>,
ext David Brownell <david-b@...bell.net>
Subject: Re: [PATCH 4/4] Add MMC Password Protection (lock/unlock) support
V9: mmc_sysfs.diff
ext Pierre Ossman wrote:
> I've queued it up for -mm, but there a few more comments I want resolved
> before this can move to Linus...
Ok, thanks for the revisions.
>
> You need to clean up mmc_lockable_store(). It had a few broken variable
> declarations that even prevented it from compiling, and after I fixed
> that I still get:
>
> drivers/mmc/mmc_sysfs.c: In function ‘mmc_lockable_store’:
> drivers/mmc/mmc_sysfs.c:160: warning: ignoring return value of
> ‘device_attach’, declared with attribute warn_unused_result
> drivers/mmc/mmc_sysfs.c:93: warning: ‘mmc_key’ may be used uninitialized
> in this function
I did a modification at this patch and did not get those warnings anymore.
>
> There's also no handling for an invalid string written to the sysfs node.
Is this really needed? I thought the function just ignored other values sent to itself that were not handled.
>
> And third, you're a bit excessive on the goto:s. E.g. out_unlocked is
> used in a single place, so it is completely unnecessary. Please do a
> general cleanup of the control flow.
Ok.
Regards,
Anderson Briglia
-
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