1. 22 9月, 2016 2 次提交
    • N
      cris: intmem: fix pointer comparison compile warning · 506823f6
      Niklas Cassel 提交于
      The code previously depended on list_head being defined
      as the first item in struct intmem_allocation.
      
      arch/cris/arch-v32/mm/intmem.c: In function ‘crisv32_intmem_free’:
      arch/cris/arch-v32/mm/intmem.c:116:14: warning: comparison of distinct pointer types lacks a cast
          if ((prev != &intmem_allocations) &&
                    ^
      arch/cris/arch-v32/mm/intmem.c:123:14: warning: comparison of distinct pointer types lacks a cast
          if ((next != &intmem_allocations) &&
                    ^
      Signed-off-by: NNiklas Cassel <nks@flawful.org>
      Signed-off-by: NJesper Nilsson <jesper.nilsson@axis.com>
      506823f6
    • J
      cris: intmem: fix device_initcall compile warning · 9d74179a
      Jesper Nilsson 提交于
      Cannot add __init macro to crisv32_intmem_init,
      since the function is being called by other functions.
      Creating a wrapper instead.
      
      arch/cris/arch-v32/mm/intmem.c: At top level:
      arch/cris/arch-v32/mm/intmem.c:148:17: warning: initialization from incompatible pointer type
       device_initcall(crisv32_intmem_init);
                       ^
      include/linux/init.h:184:58: note: in definition of macro ‘__define_initcall’
        __attribute__((__section__(".initcall" #id ".init"))) = fn; \
      
      arch/cris/arch-v32/mm/intmem.c:148:1: note: in expansion of macro ‘device_initcall’
       device_initcall(crisv32_intmem_init);
       ^
      Signed-off-by: NNiklas Cassel <nks@flawful.org>
      Signed-off-by: NJesper Nilsson <jesper.nilsson@axis.com>
      9d74179a
  2. 17 6月, 2015 1 次提交
    • P
      cris: don't use module_init for non-modular core intmem.c code · 73de14e8
      Paul Gortmaker 提交于
      The intmem.c code is always built in.  It will never be modular,
      so using module_init as an alias for __initcall is rather
      misleading.
      
      Fix this up now, so that we can relocate module_init from
      init.h into module.h in the future.  If we don't do this, we'd
      have to add module.h to obviously non-modular code, and that
      would be a worse thing.
      
      Direct use of __initcall is discouraged, vs prioritized ones.
      Use of device_initcall is consistent with what __initcall
      maps onto, and hence does not change the init order, making the
      impact of this change zero.   Should someone with real hardware
      for boot testing want to change it later to arch_initcall or
      something different, they can do that at a later date.
      Reported-by: Nkbuild test robot <fengguang.wu@intel.com>
      Cc: Mikael Starvik <starvik@axis.com>
      Cc: Jesper Nilsson <jesper.nilsson@axis.com>
      Acked-by: NJesper Nilsson <jesper.nilsson@axis.com>
      Cc: linux-cris-kernel@axis.com
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      73de14e8
  3. 16 6月, 2010 1 次提交
  4. 08 2月, 2008 1 次提交
  5. 28 7月, 2005 1 次提交