1. 07 1月, 2009 1 次提交
  2. 18 11月, 2008 5 次提交
  3. 27 10月, 2008 1 次提交
  4. 16 10月, 2008 1 次提交
  5. 09 10月, 2008 1 次提交
  6. 08 10月, 2008 1 次提交
  7. 13 8月, 2008 1 次提交
  8. 14 7月, 2008 1 次提交
  9. 25 6月, 2008 1 次提交
    • B
      Blackfin arch: fix up section mismatch warning · 8d0a6003
      Bryan Wu 提交于
      --
      WARNING: vmlinux.o(.text+0x721a): Section mismatch in reference from the function ___fill_code_cplbtab() to the function .init.text:_fill_cplbtab()
      The function ___fill_code_cplbtab() references
      the function __init _fill_cplbtab().
      This is often because ___fill_code_cplbtab lacks a __init
      annotation or the annotation of _fill_cplbtab is wrong.
      
      WARNING: vmlinux.o(.text+0x7238): Section mismatch in reference from the function ___fill_code_cplbtab() to the function .init.text:_fill_cplbtab()
      The function ___fill_code_cplbtab() references
      the function __init _fill_cplbtab().
      This is often because ___fill_code_cplbtab lacks a __init
      annotation or the annotation of _fill_cplbtab is wrong.
      
      WARNING: vmlinux.o(.text+0x7250): Section mismatch in reference from the function ___fill_code_cplbtab() to the function .init.text:_fill_cplbtab()
      The function ___fill_code_cplbtab() references
      the function __init _fill_cplbtab().
      This is often because ___fill_code_cplbtab lacks a __init
      annotation or the annotation of _fill_cplbtab is wrong.
      
      WARNING: vmlinux.o(.text+0x7264): Section mismatch in reference from the function ___fill_code_cplbtab() to the function .init.text:_fill_cplbtab()
      The function ___fill_code_cplbtab() references
      the function __init _fill_cplbtab().
      This is often because ___fill_code_cplbtab lacks a __init
      annotation or the annotation of _fill_cplbtab is wrong.
      
      WARNING: vmlinux.o(.text+0x72a2): Section mismatch in reference from the function ___fill_data_cplbtab() to the function .init.text:_fill_cplbtab()
      The function ___fill_data_cplbtab() references
      the function __init _fill_cplbtab().
      This is often because ___fill_data_cplbtab lacks a __init
      annotation or the annotation of _fill_cplbtab is wrong.
      
      WARNING: vmlinux.o(.text+0x72bc): Section mismatch in reference from the function ___fill_data_cplbtab() to the function .init.text:_fill_cplbtab()
      The function ___fill_data_cplbtab() references
      the function __init _fill_cplbtab().
      This is often because ___fill_data_cplbtab lacks a __init
      annotation or the annotation of _fill_cplbtab is wrong.
      
      WARNING: vmlinux.o(.text+0x72d4): Section mismatch in reference from the function ___fill_data_cplbtab() to the function .init.text:_fill_cplbtab()
      The function ___fill_data_cplbtab() references
      the function __init _fill_cplbtab().
      This is often because ___fill_data_cplbtab lacks a __init
      annotation or the annotation of _fill_cplbtab is wrong.
      
      WARNING: vmlinux.o(.text+0x72e8): Section mismatch in reference from the function ___fill_data_cplbtab() to the function .init.text:_fill_cplbtab()
      The function ___fill_data_cplbtab() references
      the function __init _fill_cplbtab().
      This is often because ___fill_data_cplbtab lacks a __init
      annotation or the annotation of _fill_cplbtab is wrong.
      --
      Signed-off-by: NBryan Wu <cooloney@kernel.org>
      8d0a6003
  10. 25 4月, 2008 1 次提交
  11. 24 4月, 2008 1 次提交
  12. 23 4月, 2008 1 次提交
    • M
      [Blackfin] arch: relocate MAX_SWITCH_{D,I}_CPLBS from the header to the file... · 0e184c6b
      Mike Frysinger 提交于
      [Blackfin] arch: relocate MAX_SWITCH_{D,I}_CPLBS from the header to the file where it actually gets used.
      
      relocate MAX_SWITCH_{D,I}_CPLBS from the header to the file
      where it actually gets used.  this way when we change
      CONFIG_MEM_SIZE in our kconfig, we only rebuild one or two files
      rather than a whole bunch that implicitly include cplb.h.
      
      this will also remove the ability to clear the swapcount on
      the fly, but i really dont think that functionality is important.
      
      ultimate goal is for CONFIG_MEM_SIZE to go away and calculate
      this value on the fly based on what u-boot programmed for us.
      Signed-off-by: NMike Frysinger <vapier.adi@gmail.com>
      Signed-off-by: NBryan Wu <cooloney@kernel.org>
      
      0e184c6b
  13. 11 1月, 2008 1 次提交
  14. 15 11月, 2007 1 次提交
  15. 10 10月, 2007 1 次提交
  16. 25 7月, 2007 1 次提交
  17. 12 7月, 2007 1 次提交