1. 08 9月, 2015 1 次提交
  2. 30 1月, 2008 2 次提交
    • I
      x86: lindent arch/i386/math-emu, cleanup · e8d591dc
      Ingo Molnar 提交于
      manually clean up some of the damage that lindent caused.
      (this is a separate commit so that in the unlikely case of
      a typo we can bisect it down to the manual edits.)
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      e8d591dc
    • I
      x86: lindent arch/i386/math-emu · 3d0d14f9
      Ingo Molnar 提交于
      lindent these files:
                                             errors   lines of code   errors/KLOC
       arch/x86/math-emu/                      2236            9424         237.2
       arch/x86/math-emu/                       128            8706          14.7
      
      no other changes. No code changed:
      
         text    data     bss     dec     hex filename
         5589802  612739 3833856 10036397         9924ad vmlinux.before
         5589802  612739 3833856 10036397         9924ad vmlinux.after
      
      the intent of this patch is to ease the automated tracking of kernel
      code quality - it's just much easier for us to maintain it if every file
      in arch/x86 is supposed to be clean.
      
      NOTE: it is a known problem of lindent that it causes some style damage
      of its own, but it's a safe tool (well, except for the gcc array range
      initializers extension), so we did the bulk of the changes via lindent,
      and did the manual fixups in a followup patch.
      
      the resulting math-emu code has been tested by Thomas Gleixner on a real
      386 DX CPU as well, and it works fine.
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      3d0d14f9
  3. 11 10月, 2007 1 次提交
  4. 07 12月, 2006 1 次提交
  5. 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