Re; MTD (2) Block Driver broken

Gareth Bult gareth at
Mon Mar 7 08:06:56 EST 2005

Ahh, right, that makes sense.

I re-write a driver so it works properly.

You clean up all the code I've written to the extent that it no longer
works. (was it 22 different patches?)

Code gets submitted to kernel (obviously without testing) and ends up in
the live tree as broken code.

And it it's "my" fault for not checking and fixing all YOUR changes ?!


Why am I mailing you now?

Well, firstly I have in interest in the integrity of the kernel tree -
I've been working with it and on it since 1991. Secondly, you inserted
my name into your broken code - I do not appreciate this.

What would I like, I would suggest one of;

a.    Fix your changes, TEST, and re-submit to the kernel tree
b.    Remove the new driver from the kernel tree

Either way, I would appreciate it greatly if you would remove my name
from your work.

Incidentally, there's nothing wrong with my memory (yet) and I'm still
not interested in working on the mtd driver for exactly the same reasons
as previously mentioned.

Many thanks,

On Mon, 2005-03-07 at 12:04 +0100, Jörn Engel wrote:
> On Sat, 5 March 2005 17:26:09 +0000, Gareth Bult wrote:
> > 
> > A little while back I re-wrote blkmtd.c effectively to provide proper
> > "write" access to jffs2 filesystems mounted on standard Linux block
> > devices.
> > 
> > The driver seems to have worked well (for me) and after many thousands
> > of downloads of FlashLinux, I've not had any reports of JFFS2 problems
> > or corruption.
> > 
> > It appears that someone has "cleaned up" this driver and it now appears
> > as an option in the standard kernel tree for 2.6.11.
> > 
> > Unfortunately it doesn't appear to work. As soon as you mount a JFFS2
> > filesystem on it and try to write data, corruption sets in resulting is
> > a fairly sharp system crash.
> > 
> > Copying back the source from the original driver I submitted to this
> > list and recompiling the kernel (with a one line change) appears to
> > yield a working system again.
> > 
> > So, two questions;
> > a.	Did anyone actually test the code after cleaning it up?
> > b.	Were there any life changing improvements that I really
> > 	*need* to make to the original code?
> Gareth, check your archives.
> I sent the whole list of cleanup patches to you, you could have simply
> tested them in order and told me which one broke.  Instead you got
> pissed at dwmw2 since he didn't accept your broken mails and
> explicitly told me various times, you didn't care about the driver.
> The fact that you don't remember me, you don't remember being on Cc:
> when I sent patches to Andrew Morton and now come running back is more
> than a little disturbing to me.  Va snpg, V nz frireyl cvffrq ng lbh!
> So can we pretty please both swallow our feelings and work
> constructively together?  Or should I merely treat this mail as a bug
> report, go fix it, remove every single line of your code from the
> driver and remove your name afterwards?  Both are valid options, you
> choose.
> Jörn
-- - promoting open source software in the UK
"If you have an apple and I have an apple and we exchange apples then
you and I will still each have one apple. But if you have an idea and I
have an idea and we exchange these ideas, then each of us will have two
ideas." - George Bernard Shaw

More information about the linux-mtd mailing list