From: Bas Mevissen <abuse@basmevissen.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] Debugging, Why USB is not stable
Date: Mon, 30 Aug 2010 12:13:36 +0200 [thread overview]
Message-ID: <c6e22c881ef066da145764f3f3621ba7@localhost> (raw)
In-Reply-To: <m27hj8l95t.fsf@ohwell.denx.de>
On Mon, 30 Aug 2010 11:52:30 +0200, Detlev Zundel <dzu@denx.de> wrote:
> In the past this turned out not to be as easy as it sounds. The devil
> lurks in the details which become apparent only when starting on the
> job. But of course if somebody accomplishes this, I cannot imagine
> anyone from stopping him :)
>
Well, I vaguely recall a recent discussion here where a lot of changes
to imported code were requested just to fulfil the U-boot code
guidelines. That will not help particularly when the code needs to be
synced again with the origin.
And yes, nobody said it was easy :-)
--
Bas
next prev parent reply other threads:[~2010-08-30 10:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 23:12 [U-Boot] Debugging, Why USB is not stable Gérald Kerma
2010-08-30 9:12 ` Detlev Zundel
2010-08-30 9:37 ` Bas Mevissen
2010-08-30 9:52 ` Detlev Zundel
2010-08-30 10:13 ` Bas Mevissen [this message]
2010-08-30 10:20 ` Detlev Zundel
2010-08-31 18:12 ` Remy Bohmer
2010-09-01 15:15 ` Detlev Zundel
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=c6e22c881ef066da145764f3f3621ba7@localhost \
--to=abuse@basmevissen.nl \
--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