1. 08 12月, 2013 1 次提交
    • G
      m68k/amiga,atari: Fix specifying multiple debug= parameters · 8a09cec2
      Geert Uytterhoeven 提交于
      Since commit d6713b40 ("m68k: early
      parameter support"), the user can specify multiple debug consoles using the
      "debug=" kernel command line parameter.
      However, as there's only a single struct console object, which is reused,
      it would actually register the same console object multiple times, causing
      the following warning:
      
      WARNING: CPU: 0 PID: 0 at kernel/printk/printk.c:2233 register_console+0x36/
      console 'debug0' already registered
      
      Make sure to register the console object only once, to avoid the warning.
      
      Note that still only one console (the one corresponding to the last
      "debug=" parameter) will be active at the same time, as the .write() method
      of the already registered console object is overwritten by a subsequent
      "debug=" parameter.
      Signed-off-by: NGeert Uytterhoeven <geert@linux-m68k.org>
      8a09cec2
  2. 11 12月, 2011 1 次提交
  3. 23 1月, 2011 1 次提交
    • G
      m68k/atari: Rename "scc" to "atari_scc" · de339e4b
      Geert Uytterhoeven 提交于
      It's a way too generic name for a global #define and conflicts with a variable
      with the same name, causing build errors like:
      
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c: In function ‘_si_clkctl_cc’:
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1364: error: expected identifier or ‘(’ before ‘volatile’
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1364: error: expected ‘)’ before ‘(’ token
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1421: error: incompatible types in assignment
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1422: error: invalid operands to binary &
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1423: error: invalid operands to binary &
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1424: error: invalid operands to binary |
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1425: error: aggregate value used where an integer was expected
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1425: error: aggregate value used where an integer was expected
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1425: error: aggregate value used where an integer was expected
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1425: error: aggregate value used where an integer was expected
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1425: error: aggregate value used where an integer was expected
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1425: error: aggregate value used where an integer was expected
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1425: error: aggregate value used where an integer was expected
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1425: error: aggregate value used where an integer was expected
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1425: error: aggregate value used where an integer was expected
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1425: error: aggregate value used where an integer was expected
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1425: error: aggregate value used where an integer was expected
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1425: error: incompatible type for argument 4 of ‘bcmsdh_reg_write’
      | drivers/staging/brcm80211/brcmfmac/../util/siutils.c:1428: error: invalid operands to binary &
      | make[8]: *** [drivers/staging/brcm80211/brcmfmac/../util/siutils.o] Error 1
      Signed-off-by: NGeert Uytterhoeven <geert@linux-m68k.org>
      de339e4b
  4. 23 2月, 2009 1 次提交
  5. 21 7月, 2008 1 次提交
  6. 06 2月, 2008 1 次提交
  7. 05 5月, 2007 2 次提交
  8. 01 7月, 2006 1 次提交
  9. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4