- 16 May, 2006 1 commit
-
-
David Woodhouse authored
We all inherited the same error from the original NAND board driver which got copied and changed. Fix them all at once... Signed-off-by:
David Woodhouse <dwmw2@infradead.org>
-
- 14 May, 2006 1 commit
-
-
David Woodhouse authored
The _board_ driver needs to be mtd->owner, and it in turn pins the nand.ko module. Fix them all to actually do that, and fix nand.ko not to overwrite it -- and also to check that the caller sets it, if the caller is a module. Signed-off-by:
David Woodhouse <dwmw2@infradead.org>
-
- 13 May, 2006 1 commit
-
-
David Woodhouse authored
It was just too painful to deal with. Signed-off-by:
David Woodhouse <dwmw2@infradead.org>
-
- 10 Jan, 2006 1 commit
-
-
Jesper Juhl authored
ICC likes to complain about storage class not being first, GCC doesn't care much (except for cases like "inline static"). have a hard time seeing how it could break anything. Thanks to Gabriel A. Devenyi for pointing out http://linuxicc.sourceforge.net/ which is what made me create this patch. Signed-off-by:
Jesper Juhl <jesper.juhl@gmail.com> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
- 07 Nov, 2005 1 commit
-
-
Thomas Gleixner authored
Signed-off-by:
Thomas Gleixner <tglx@linutronix.de>
-
- 23 May, 2005 2 commits
-
-
David A. Marlin authored
Added routine to perform extra error status checks on erase and write failures to determine if errors are correctable. Added option to prevent JFFS2 from using virtual erase blocks. Performed minor cleanup on whitespace and comments. Signed-off-by:
David A. Marlin <dmarlin@redhat.com> Signed-off-by:
Thomas Gleixner <tglx@linutronix.de>
-
David A. Marlin authored
Add routine to perform device recovery (deplete) procedure. Clean up some compiler warnings. Signed-off-by:
David A. Marlin <dmarlin@redhat.com> Signed-off-by:
Thomas Gleixner <tglx@linutronix.de>
-
- 16 Apr, 2005 1 commit
-
-
Linus Torvalds authored
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!
-