From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Gareth Bult <gareth@linux.co.uk>
Cc: Linux MTD <linux-mtd@lists.infradead.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: Re; MTD (2) Block Driver broken
Date: Mon, 7 Mar 2005 23:33:29 +0100 [thread overview]
Message-ID: <20050307223329.GG26318@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1110233417.11311.58.camel@squizzey.bult.co.uk>
On Mon, 7 March 2005 22:10:17 +0000, Gareth Bult wrote:
>
> When I get time I'll test it. If it works, I may even use it. I'm not
> however desperate to have my name on it. Everyone screws up code - it's
> not a problem .. submitting changed code however without testing it is a
> little .. overconfident (?)
When I wrote it, I lacked the hardware to test it. Then I tested it
with mtdblock, and it worked. Then I tested it with jffs2 and that
didn't work. I suspected jffs2, spent a week (about 50-60 hours) on
that one, wrote 34 seperate patches for jffs2 and still couldn't find
it.
Bug was actually in block2mtd, mtdblock just didn't trigger it. Darn!
Only after testing did I submit the code to cvs, so I was not
overconfident. Stupid is more to the point.
> I don't work on code for credit, I work on it because I enjoy it.
Well, the credit is free advertisement. On the next job interview, a
"just grep the kernel sources" comment explains my qualifications and
may keep me from unemployment here or raise my salary there.
Credit is never the reason to write code in the first place. My
block2mtd patches were written for fun and because I would like to
replace my hard driver with a USB key. But the free extra doesn't
hurt, at least until I win the lottery (and I never play).
Jörn
--
Don't patch bad code, rewrite it.
-- Kernigham and Pike, according to Rusty
next prev parent reply other threads:[~2005-03-07 22:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 17:26 Re; MTD (2) Block Driver broken Gareth Bult
2005-03-07 11:04 ` Jörn Engel
2005-03-07 11:13 ` Jörn Engel
2005-03-07 12:45 ` Josh Boyer
2005-03-07 12:52 ` Jörn Engel
2005-03-07 13:06 ` Gareth Bult
2005-03-07 14:24 ` Jörn Engel
2005-03-07 18:34 ` Gareth Bult
2005-03-07 19:00 ` Jörn Engel
[not found] ` <1110222770.11437.51.camel@squizzey.bult.co.uk>
2005-03-07 19:15 ` Jörn Engel
2005-03-07 20:42 ` Jörn Engel
2005-03-07 20:21 ` David Woodhouse
2005-03-07 20:57 ` Gareth Bult
2005-03-07 21:07 ` Jörn Engel
2005-03-07 21:46 ` Gareth Bult
2005-03-07 22:01 ` Jörn Engel
2005-03-07 22:20 ` Gareth Bult
2005-03-07 22:42 ` Jörn Engel
2005-03-08 10:33 ` Gareth Bult
2005-03-08 10:44 ` Jörn Engel
2005-03-07 21:26 ` David Woodhouse
2005-03-07 22:10 ` Gareth Bult
2005-03-07 22:20 ` David Woodhouse
2005-03-07 22:26 ` Gareth Bult
2005-03-07 22:30 ` David Woodhouse
2005-03-08 10:24 ` Gareth Bult
2005-03-08 11:05 ` David Woodhouse
2005-03-08 11:27 ` Gareth Bult
2005-03-07 22:33 ` Jörn Engel [this message]
2005-03-08 10:31 ` Gareth Bult
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050307223329.GG26318@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=dwmw2@infradead.org \
--cc=gareth@linux.co.uk \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox