1. 29 3月, 2013 2 次提交
  2. 28 3月, 2013 1 次提交
    • E
      arm: sunxi: rename clock compatible strings · fd9d9915
      Emilio López 提交于
      During the introduction of the Allwinner SoC platforms, sunxi was
      initially meant as a generic name for all the variants of the Allwinner
      SoC.
      
      It was ok at the time of the support of only the A10 and A13 that
      look pretty much the same; but it's beginning to be troublesome with
      the future addition of the Allwinner A31 (sun6i) that is quite
      different, and would introduce some weird logic, where sunxi would
      actually mean in some case sun4i and sun5i but without sun6i...
      
      Moreover, it makes the compatible strings naming scheme not consistent
      with other architectures, where usually for this kind of compability, we
      just use the oldest SoC name that has this IP, so let's do just this.
      Signed-off-by: NEmilio López <emilio@elopez.com.ar>
      Signed-off-by: NMaxime Ripard <maxime.ripard@free-electrons.com>
      fd9d9915
  3. 23 3月, 2013 1 次提交
  4. 10 3月, 2013 1 次提交
  5. 06 3月, 2013 3 次提交
  6. 02 3月, 2013 1 次提交
    • R
      ARM: Fix broken commit 0cc41e4a corrupting kernel messages · ded3ef0f
      Russell King 提交于
      Commit 0cc41e4a (arch: remove direct definitions of KERN_<LEVEL>
      uses) is broken - not enough thought was put into changing:
      
      	.asciz	"string"
      
      to
      
      	.asciz	"string1" "string2"
      
      The problem is that each string gets _separately_ NUL terminated, so
      the result is a string containing:
      
      	"string1\0string2\0"
      
      rather than:
      
      	"string1string2\0"
      
      With our new printk levels, this ends up as - eg, KERN_DEBUG "string":
      
      	0x01 0x00 0x07 0x00 "string" 0x00
      
      which produces lots of \x01 in the kernel log.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      ded3ef0f
  7. 01 3月, 2013 31 次提交