1. 11 7月, 2016 2 次提交
  2. 04 7月, 2016 1 次提交
  3. 27 6月, 2016 1 次提交
  4. 20 6月, 2016 1 次提交
  5. 17 6月, 2016 4 次提交
  6. 06 6月, 2016 3 次提交
  7. 01 6月, 2016 2 次提交
  8. 30 5月, 2016 5 次提交
  9. 18 5月, 2016 1 次提交
    • A
      ARM: exynos: don't select keyboard driver · 8a6f71cc
      Arnd Bergmann 提交于
      The samsung-keypad driver is implicitly selected by ARCH_EXYNOS4 (why?),
      but this fails if CONFIG_INPUT is a loadable module:
      
      drivers/input/built-in.o: In function `samsung_keypad_remove':
      drivers/input/keyboard/samsung-keypad.c:461: undefined reference to `input_unregister_device'
      drivers/input/built-in.o: In function `samsung_keypad_irq':
      drivers/input/keyboard/samsung-keypad.c:137: undefined reference to `input_event'
      drivers/input/built-in.o: In function `samsung_keypad_irq':
      include/linux/input.h:389: undefined reference to `input_event'
      drivers/input/built-in.o: In function `samsung_keypad_probe':
      drivers/input/keyboard/samsung-keypad.c:358: undefined reference to `devm_input_allocate_device'
      drivers/input/built-in.o:(.debug_addr+0x34): undefined reference to `input_set_capability'
      
      This removes the 'select' as suggested by Krzysztof Kozlowski and
      instead enables the driver from the defconfig files.
      
      The problem does not happen on mainline kernels, as we don't normally
      build built-in input drivers when CONFIG_INPUT=m, but I am experimenting
      with a patch to change this, and the samsung keypad driver showed up
      as one example that was silently broken before.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Link: https://lkml.org/lkml/2016/2/14/55Signed-off-by: NKrzysztof Kozlowski <k.kozlowski@samsung.com>
      8a6f71cc
  10. 10 5月, 2016 1 次提交
  11. 30 4月, 2016 1 次提交
  12. 27 4月, 2016 5 次提交
  13. 26 4月, 2016 1 次提交
  14. 22 4月, 2016 1 次提交
  15. 15 4月, 2016 1 次提交
  16. 14 4月, 2016 2 次提交
  17. 12 4月, 2016 1 次提交
  18. 07 4月, 2016 1 次提交
  19. 06 4月, 2016 3 次提交
  20. 05 4月, 2016 3 次提交