On Tue, Mar 11, 2014 at 09:32:35PM +0000, Jason Cooper wrote: > These are the minimum changes required to get the code to build > statically in the kernel. It's necessary to do this first so that we > can empirically determine that future cleanup patches aren't changing > the generated object code. > > Signed-off-by: Jason Cooper <jason@xxxxxxxxxxxxxx> This doesn't apply to my latest tree :( > --- a/drivers/staging/Makefile > +++ b/drivers/staging/Makefile > @@ -65,3 +65,4 @@ obj-$(CONFIG_XILLYBUS) += xillybus/ > obj-$(CONFIG_DGNC) += dgnc/ > obj-$(CONFIG_DGAP) += dgap/ > obj-$(CONFIG_MTD_SPINAND_MT29F) += mt29f_spinand/ > +obj-$(CONFIG_CRYPTO_SKEIN) += skein/ Care to align these up with the way this file is formatted? And I have no objection to taking the drivers/staging/ patches, the script looks useful, but I can't take it through the staging tree, sorry. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
