summaryrefslogtreecommitdiffstats
path: root/arch/m68k/configs/q40_defconfig
Commit message (Collapse)AuthorAgeFilesLines
* m68k: Update defconfigs for 2.6.28-rc7Geert Uytterhoeven2008-12-021-53/+72
| | | | Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
* m68k: Update defconfigs for 2.6.27-rc6Geert Uytterhoeven2008-09-101-21/+32
| | | | | Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
* m68k: enable CONFIG_COMPAT_BRK by defaultGeert Uytterhoeven2008-06-061-3/+3
| | | | | | | | | As some m68k machines have plenty of libc5 binaries in active use, enable CONFIG_COMPAT_BRK by default. Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
* m68k: Update defconfigsGeert Uytterhoeven2008-05-181-68/+91
| | | | | | | Update the m68k defconfigs Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
* m68k: update defconfigs for 2.6.25Geert Uytterhoeven2008-04-041-420/+571
| | | | | | | Long overdue update of the m68k defconfigs Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
* [PATCH] M68k: Update defconfigsGeert Uytterhoeven2005-06-131-11/+4Star
| | | | | Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
* [PATCH] M68k: Update defconfigs for 2.6.12-rc2Geert Uytterhoeven2005-04-181-25/+36
| | | | | | Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
* [PATCH] M68k: Update defconfigs for 2.6.11Geert Uytterhoeven2005-04-181-6/+27
| | | | | | Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
* Linux-2.6.12-rc2Linus Torvalds2005-04-171-0/+915
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!