1. 15 8月, 2009 1 次提交
  2. 02 6月, 2009 1 次提交
  3. 22 12月, 2008 1 次提交
  4. 06 3月, 2008 1 次提交
  5. 28 1月, 2008 4 次提交
  6. 21 9月, 2007 2 次提交
  7. 11 6月, 2007 1 次提交
  8. 07 5月, 2007 1 次提交
    • P
      sh: speculative execution support for SH7780. · 45ed285b
      Paul Mundt 提交于
      SH7780 has a speculative execution mode where it can speculatively
      perform an instruction fetch for subroutine returns, this allows it
      to be enabled. There are some various pitfalls associated with this
      mode, so it's left as depending on CONFIG_EXPERIMENTAL and not
      enabled by default.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      45ed285b
  9. 12 3月, 2007 1 次提交
  10. 13 2月, 2007 2 次提交
  11. 06 12月, 2006 1 次提交
  12. 27 9月, 2006 2 次提交
  13. 01 4月, 2006 1 次提交
    • O
      [PATCH] Don't pass boot parameters to argv_init[] · 9b41046c
      OGAWA Hirofumi 提交于
      The boot cmdline is parsed in parse_early_param() and
      parse_args(,unknown_bootoption).
      
      And __setup() is used in obsolete_checksetup().
      
      	start_kernel()
      		-> parse_args()
      			-> unknown_bootoption()
      				-> obsolete_checksetup()
      
      If __setup()'s callback (->setup_func()) returns 1 in
      obsolete_checksetup(), obsolete_checksetup() thinks a parameter was
      handled.
      
      If ->setup_func() returns 0, obsolete_checksetup() tries other
      ->setup_func().  If all ->setup_func() that matched a parameter returns 0,
      a parameter is seted to argv_init[].
      
      Then, when runing /sbin/init or init=app, argv_init[] is passed to the app.
      If the app doesn't ignore those arguments, it will warning and exit.
      
      This patch fixes a wrong usage of it, however fixes obvious one only.
      Signed-off-by: NOGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      9b41046c
  14. 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