From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] What if eth_init() fails?
Date: Wed, 14 Nov 2007 12:00:03 -0500 [thread overview]
Message-ID: <200711141200.03914.vapier@gentoo.org> (raw)
In-Reply-To: <473B2817.8040504@freescale.com>
On Wednesday 14 November 2007, Timur Tabi wrote:
> Mike Frysinger wrote:
> > so by fixing one bug, you may expose other bugs, and that's a bad thing ?
> > bad code has gotta go !
>
> My point was that if you fix this bug, you should be prepared for other
> bugs to show up, and people to be surprised about it. Don't just fix the
> first bug and walk away. If you can't test all the other platforms, then
> you should at least pay attention when other people report the other bugs,
> and then help them out.
i'd say it is the fault of those platforms for having bad code in the first
place ... cant reasonably expect Upakul to audit and fix everyone's mistakes.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20071114/002769c6/attachment.pgp
next prev parent reply other threads:[~2007-11-14 17:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 6:21 [U-Boot-Users] What if eth_init() fails? Upakul Barkakaty
2007-11-14 11:07 ` Detlev Zundel
2007-11-16 6:13 ` Upakul Barkakaty
2007-11-16 12:29 ` Detlev Zundel
2007-11-16 16:27 ` Detlev Zundel
2007-11-16 16:35 ` Wolfgang Denk
2007-11-14 15:08 ` Ben Warren
2007-11-14 15:24 ` Timur Tabi
2007-11-14 16:49 ` Mike Frysinger
2007-11-14 16:53 ` Timur Tabi
2007-11-14 17:00 ` Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-19 4:37 Upakul Barkakaty
2007-11-19 13:26 ` Wolfgang Denk
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=200711141200.03914.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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