| Message ID | 20191003031312.313485229@gmail.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | scripts: update namespace.pl | expand |
On Thu, Oct 3, 2019 at 12:18 PM <rd.dunlab@gmail.com> wrote: You can grow %nmexception until you no longer see "No nm data for ..." messages, but is this maintainable? I think it is more realistic to delete the printf "No nm data for $fullname\n" line.
--- linux-next-20191002.orig/scripts/namespace.pl +++ linux-next-20191002/scripts/namespace.pl @@ -91,6 +91,8 @@ my %nmexception = ( 'arch/x86/lib/thunk_32' => 1, 'arch/x86/lib/cmpxchg' => 1, 'arch/x86/vdso/vdso32/note' => 1, + 'arch/x86/entry/vdso/vdso-note.o' => 1, + 'arch/x86/entry/vdso/vdso32/note.o' => 1, 'lib/irq_regs' => 1, 'usr/initramfs_data' => 1, 'drivers/scsi/aic94xx/aic94xx_dump' => 1,
These x86 object files do not have any exports or public symbols so they can be excluded from the namespace checking. Signed-off-by: Randy Dunlap <rd.dunlab@gmail.com> Cc: Masahiro Yamada <yamada.masahiro@socionext.com> Cc: Randy Dunlap <rdunlap@infradead.org> --- patch 2/4: scripts/namespace.pl | 2 ++ 1 file changed, 2 insertions(+)