Herbert Xu wrote: > On Mon, May 22, 2006 at 03:10:38PM +1200, Michal Ludvig wrote: >> Well, not personally, but padlock-sha will. > > How is it going to use these accessors? I'd like to see some code :)
The driver_name accessor is used "seriously". The priority accessor is just in one info printk() so it isn't necessary. >> BTW in padlock fallback path I need to make scatterlist from const char* >> buffer. However the macros in scatterlist.h take non-const void*. >> Should I >> 1) make them const (works for me and I'm not getting any compilation >> warnings from other modules). >> 2) make my local copy of sg_set_buf() with const void parameter >> 3) let gcc keep complaining > > Please show me the code that causes this problem. See my other e-mail with the patch. sg_set_buf() in padlock_sha_update() causes the gcc warning. Michal - To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
