Skip to content
Snippets Groups Projects
Select Git revision
  • 221cc2d27ddc49b3e06d4637db02bf78e70c573c
  • vme-testing default
  • ci-test
  • master
  • remoteproc
  • am625-sk-ov5640
  • pcal6534-upstreaming
  • lps22df-upstreaming
  • msc-upstreaming
  • imx8mp
  • iio/noa1305
  • vme-next
  • vme-next-4.14-rc4
  • v4.14-rc4
  • v4.14-rc3
  • v4.14-rc2
  • v4.14-rc1
  • v4.13
  • vme-next-4.13-rc7
  • v4.13-rc7
  • v4.13-rc6
  • v4.13-rc5
  • v4.13-rc4
  • v4.13-rc3
  • v4.13-rc2
  • v4.13-rc1
  • v4.12
  • v4.12-rc7
  • v4.12-rc6
  • v4.12-rc5
  • v4.12-rc4
  • v4.12-rc3
32 results

mod

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Masahiro Yamada authored
    Unless CONFIG_DEBUG_SECTION_MISMATCH is enabled, modpost only shows
    the number of section mismatches.
    
    If you want to know the symbols causing the issue, you need to rebuild
    with CONFIG_DEBUG_SECTION_MISMATCH. It is tedious.
    
    I think it is fine to show annoying warning when a new section mismatch
    comes in.
    
    Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
    46c7dd56
    History
    Name Last commit Last update
    ..