From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 4/8] common: spl: Add interactive DDR debugger support for SPL image
Date: Mon, 17 Nov 2014 15:00:42 -0800 [thread overview]
Message-ID: <546A7E1A.3030607@freescale.com> (raw)
In-Reply-To: <1d5a39b148ad4119b71d81e4b4a6e391@BN1PR0301MB0689.namprd03.prod.outlook.com>
On 10/27/2014 06:48 PM, Wang Huan-B18965 wrote:
> Hello, Albert,
>
<snip>
>>> ---
>>> Change log:
>>> v3: Gave more explaination in the commit.
>>> v2: No change.
>>
>> This does not apply cleanly. Could you rebase and resubmit?
> [Alison Wang] ok, I will rebase and resubmit the set. Thanks.
>
Alison,
Where are we on this patch? If you haven't sent an update, I can take this one
and resolve the conflict.
Albert,
This set primarily deals with FSL specific boards. I can take them in if you
don't see any issue with the patches (except the conflicts).
York
next prev parent reply other threads:[~2014-11-17 23:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 8:00 [U-Boot] [PATCH v3 0/8] Add SD/NAND boot support for LS1021AQDS/TWR board Alison Wang
2014-10-17 8:00 ` [U-Boot] [PATCH v3 1/8] ls102xa: pblimage: Add pblimage tool support for LS102xA Alison Wang
2014-10-17 8:00 ` [U-Boot] [PATCH v3 2/8] spl: Use u-boot.img instead of u-boot.bin Alison Wang
2014-10-17 8:00 ` [U-Boot] [PATCH v3 3/8] arm: spl: Add I2C linker list in generic .lds Alison Wang
2014-10-17 8:00 ` [U-Boot] [PATCH v3 4/8] common: spl: Add interactive DDR debugger support for SPL image Alison Wang
2014-10-27 9:29 ` Albert ARIBAUD
2014-10-28 1:48 ` Huan Wang
2014-11-17 23:00 ` York Sun [this message]
2014-11-18 7:02 ` Albert ARIBAUD
2014-11-18 17:07 ` York Sun
2014-12-01 19:07 ` York Sun
2014-12-03 7:15 ` Huan Wang
2014-10-28 15:31 ` York Sun
2014-10-17 8:00 ` [U-Boot] [PATCH v3 5/8] ls102xa: qixis: Add CONFIG_QIXIS_I2C_ACCESS macro Alison Wang
2014-10-17 8:00 ` [U-Boot] [PATCH v3 6/8] arm: ls102xa: Add SD boot support for LS1021AQDS board Alison Wang
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=546A7E1A.3030607@freescale.com \
--to=yorksun@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