lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 17 Feb 2007 18:07:46 -0500 From: Theodore Tso <tytso@....edu> To: Artem Bityutskiy <dedekind@...radead.org> Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Christoph Hellwig <hch@...radead.org>, Frank Haverkamp <haver@...t.ibm.com>, Josh Boyer <jwboyer@...ux.vnet.ibm.com>, Thomas Gleixner <tglx@...utronix.de>, David Woodhouse <dwmw2@...radead.org> Subject: Re: [PATCH 15/44 take 2] [UBI] scanning unit header On Sat, Feb 17, 2007 at 06:55:40PM +0200, Artem Bityutskiy wrote: > +/** > + * ubi_scan_erase_peb - erase a physical eraseblock. > + * > + * @ubi: the UBI device description object > + * @si: a pointer to the scanning information > + * @pnum: physical eraseblock number to erase; > + * @ec: erase counter value to write (%NAND_SCAN_UNKNOWN_EC if it is unknown) > + * > + * This function erases physical eraseblock 'pnum', and writes the erase > + * counter header to it. This function should only be used on UBI device > + * initialization stages, when the EBA unit had not been yet initialized. This > + * function returns zero in case of success and a negative error code in case > + * of failure. > + */ This is a general comment that applies across your entire patchset. It would be a lot easier to review the patchset if you put the Docbook description of the function with the .c file instead of the .h file. This will also make it much more likely that when you or other people update the code function, that the documentation will get updated as well. I'd recommend doing this along with combining all of your *.h files into a ubi_private.h and ubi.h file. Regards, - Ted - 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