From: Tang Yuantian <Yuantian.Tang@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] test
Date: Mon, 17 Feb 2014 17:18:51 +0800 [thread overview]
Message-ID: <5301D3FB.7000104@freescale.com> (raw)
In-Reply-To: <1392418747.6733.626.camel@snotra.buserror.net>
test.
? 2014/2/15 ??? 6:59, Scott Wood ??:
> On Thu, 2014-02-13 at 02:12 -0600, Tang Yuantian-B29983 wrote:
>>> Use an I/O accessor.
>> In_be64?? No such function.
> Why do you need in_be64() rather than two in_be32()s?
>
> -Scott
>
>
next prev parent reply other threads:[~2014-02-17 9:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 6:00 [U-Boot] [PATCH 1/3] mpc85xx: Add support for the supplement configuration unit register Tang Yuantian
2014-01-26 6:00 ` [U-Boot] [PATCH 2/3] mpc85xx: Add deep sleep framework support Tang Yuantian
2014-02-13 0:44 ` [U-Boot] [U-Boot, " Scott Wood
[not found] ` <07dc877206434a4ea634d912c02da3a5@BL2PR03MB115.namprd03.prod.outlook.com>
2014-02-14 22:21 ` Scott Wood
2014-02-24 7:47 ` Tang Yuantian-B29983
2014-02-24 19:11 ` Scott Wood
2014-02-26 7:49 ` Tang Yuantian-B29983
2014-02-26 8:13 ` Tang Yuantian-B29983
[not found] ` <c321feb926884bca922904aec215fdff@BL2PR03MB115.namprd03.prod.outlook.com>
2014-02-14 22:59 ` Scott Wood
2014-02-17 9:18 ` Tang Yuantian [this message]
[not found] ` <95751c79b09a4a15a7b4d577fd86ff3e@BL2PR03MB115.namprd03.prod.outlook.com>
2014-02-17 19:18 ` Scott Wood
2014-02-24 6:44 ` Tang Yuantian-B29983
2014-02-24 19:11 ` Scott Wood
2014-02-26 5:52 ` Tang Yuantian-B29983
2014-01-26 6:00 ` [U-Boot] [PATCH 3/3] mpc85xx: Add deep sleep support on T1040QDS Tang Yuantian
-- strict thread matches above, loose matches on Subject: below --
2015-04-24 14:39 [U-Boot] Test Hannes Petermaier
2015-04-25 10:03 ` Nable
2014-02-24 7:26 [U-Boot] test Yuantian Tang
2013-11-07 9:21 Igor Grinberg
2009-09-03 21:51 [U-Boot] TEST Wolfgang Denk
2009-07-30 11:43 [U-Boot] Test Tuma
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=5301D3FB.7000104@freescale.com \
--to=yuantian.tang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.