On Fri, 22 May 2015, Minfei Huang wrote: > Usually we prefer to let compiler put the module initialized function to > section ".init.text". Thus this text in memory will be freed in future. > > Once we add the "__init" preceding function name, we can use following > command to find it in specfied section. > > $ objdump -t -j .init.text built-in.o > > built-in.o: file format elf64-x86-64 > > SYMBOL TABLE: > 0000000000000000 l d .init.text 0000000000000000 .init.text > 0000000000000000 l F .init.text 000000000000004e klp_init > > Signed-off-by: Minfei Huang <mnfhuang@xxxxxxxxx> I think this changelog is way too verbose for no good reason (this is probably the first time in my life I am saying something like that :) ). There is really no need to explain how to use objdump in changelog. I've shortened the changelog and applied. Thanks, -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe live-patching" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
