summaryrefslogtreecommitdiffstats
path: root/lib/seq_buf.c
diff options
context:
space:
mode:
authorJessica Yu <jeyu@kernel.org>2018-11-19 17:43:58 +0100
committerJessica Yu <jeyu@kernel.org>2018-11-29 14:24:13 +0100
commit2d25bc55235314d869459c574be14e8faa73aca3 (patch)
tree33cd8f3c2480d8f1bb02f8151d2b2af0f61c5c50 /lib/seq_buf.c
parente84cd7ee630e44a2cc8ae49e85920a271b214cb3 (diff)
downloadlinux-2d25bc55235314d869459c574be14e8faa73aca3.tar.bz2
module: make it clearer when we're handling kallsyms symbols vs exported symbols
The module loader internally works with both exported symbols represented as struct kernel_symbol, as well as Elf symbols from a module's symbol table. It's hard to distinguish sometimes which type of symbol we're handling given that some helper function names are not consistent or helpful. Take get_ksymbol() for instance - are we looking for an exported symbol or a kallsyms symbol here? Or symname() and kernel_symbol_name() - which function handles an exported symbol and which one an Elf symbol? Clean up and unify the function naming scheme a bit to make it clear which kind of symbol we're handling. This change only affects static functions internal to the module loader. Reviewed-by: Miroslav Benes <mbenes@suse.cz> Signed-off-by: Jessica Yu <jeyu@kernel.org>
Diffstat (limited to 'lib/seq_buf.c')
0 files changed, 0 insertions, 0 deletions