From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Please pull from 'mpc83xx' branch
Date: Thu, 01 Feb 2007 11:18:21 -0600 [thread overview]
Message-ID: <45C220DD.8020005@freescale.com> (raw)
In-Reply-To: <A2D6E200-D73D-4C2F-9CCF-550F18AA7D5E@kernel.crashing.org>
Kumar Gala wrote:
> Kim asked me to clean up the original patch because of the issues you
> pointed out, that's been done. Anything beyond that I'll leave up to
> you guys.
Fair enough. I just wish I could find that email about USB clocks.
I'll run some tests on the 8349ITX to see what it thinks about the default clocks.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-02-01 17:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 21:34 [U-Boot-Users] Please pull from 'mpc83xx' branch Kumar Gala
2007-01-30 22:37 ` Wolfgang Denk
2007-01-30 22:49 ` Timur Tabi
2007-01-30 22:55 ` Kumar Gala
2007-01-31 0:26 ` Wolfgang Denk
2007-01-31 23:04 ` Timur Tabi
2007-02-01 4:26 ` Kumar Gala
2007-02-01 16:06 ` Timur Tabi
2007-02-01 16:39 ` Kumar Gala
2007-02-01 17:18 ` Timur Tabi [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-05 21:51 Kumar Gala
2006-12-14 22:18 ` Timur Tabi
2006-12-14 22:44 ` Kumar Gala
2006-12-14 22:47 ` Timur Tabi
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=45C220DD.8020005@freescale.com \
--to=timur@freescale.com \
--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