1. 19 1月, 2011 1 次提交
  2. 01 10月, 2010 1 次提交
  3. 20 4月, 2010 1 次提交
  4. 23 1月, 2010 1 次提交
  5. 21 9月, 2009 1 次提交
    • F
      x86: Trivial whitespace cleanups · 878f4f53
      Felipe Contreras 提交于
      Signed-off-by: NFelipe Contreras <felipe.contreras@gmail.com>
      Cc: Vegard Nossum <vegardno@ifi.uio.no>
      Cc: Pekka Enberg <penberg@cs.helsinki.fi>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: Alok N Kataria <akataria@vmware.com>
      Cc: "Tan Wei Chong" <wei.chong.tan@intel.com>
      Cc: Len Brown <len.brown@intel.com>
      Cc: Lin Ming <ming.m.lin@intel.com>
      Cc: Bob Moore <robert.moore@intel.com>
      LKML-Reference: <1253137123-18047-2-git-send-email-felipe.contreras@gmail.com>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      878f4f53
  6. 27 5月, 2009 2 次提交
  7. 28 3月, 2009 3 次提交
  8. 27 3月, 2009 4 次提交
  9. 09 1月, 2009 2 次提交
  10. 31 12月, 2008 4 次提交
  11. 30 12月, 2008 2 次提交
  12. 07 11月, 2008 1 次提交
  13. 11 10月, 2008 1 次提交
    • J
      ACPI: fix FADT parsing · fcea94ba
      Jan Beulich 提交于
      The (1.0 inherited) separate length fields in the FADT are byte granular.
      Further, PM1a/b may have distinct lengths (if using the v2 fields was
      okay) and may live in distinct address spaces.  acpi_tb_convert_fadt()
      should account for all of these conditions.
      
      Apart from these changes I'm puzzled by the fact that, not just for
      acpi_gbl_xpm1{a,b}_enable, acpi_hw_low_level_{read,write}() get an
      explicit size passed rather than using the size found in the passed GAS.
      What happens on a platform that defines PM1{a,b} wider than 16 bits?  Of
      course, acpi_hw_low_level_{read,write}() at present are entirely
      un-prepared to deal with sizes other than 8, 16, or 32, not to speak of a
      non-zero bit_offset or access_width...
      Signed-off-by: NJan Beulich <jbeulich@novell.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      fcea94ba
  14. 18 7月, 2008 1 次提交
  15. 17 7月, 2008 2 次提交
  16. 24 4月, 2008 1 次提交
  17. 03 7月, 2007 1 次提交
  18. 10 5月, 2007 1 次提交
  19. 29 4月, 2007 1 次提交
  20. 03 2月, 2007 7 次提交