All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Chou <thomas@wytron.com.tw>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/2] common/board_f.c: move mark_bootstage after arch_cpu_init_dm
Date: Fri, 6 Nov 2015 12:08:58 +0800	[thread overview]
Message-ID: <563C27DA.3060106@wytron.com.tw> (raw)
In-Reply-To: <CAPnjgZ2SAGHJN9uA9dhOpwGzMjc+weh1kxDQfUnVfmFam-vwWw@mail.gmail.com>

Hi Simon,

On 2015?11?06? 11:15, Simon Glass wrote:
> On 30 October 2015 at 01:35, Thomas Chou <thomas@wytron.com.tw> wrote:
>> As mark_bootstage() uses timer, it should go after driver model
>> is initialized.
>>
>> Signed-off-by: Thomas Chou <thomas@wytron.com.tw>
>> Reviewed-by: Simon Glass <sjg@chromium.org>
>> ---
>>   common/board_f.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> Reviewed-by: Simon Glass <sjg@chromium.org>
>

Will you please pick up this series? Or shall I pick them? As Bin Meng 
has follow up patches to timer uclass, I hope we can resolve rebase issue.

Best regards,
Thomas

  reply	other threads:[~2015-11-06  4:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 13:25 [U-Boot] [PATCH] sandbox: add a sandbox timer and basic test Thomas Chou
2015-10-29 17:16 ` Simon Glass
2015-10-29 23:27   ` Thomas Chou
2015-10-29 23:43     ` Simon Glass
2015-10-30  6:08       ` Thomas Chou
2015-10-30  7:35 ` [U-Boot] [PATCH v2 1/2] common/board_f.c: move mark_bootstage after arch_cpu_init_dm Thomas Chou
2015-10-30  7:35   ` [U-Boot] [PATCH v2 2/2] sandbox: add a sandbox timer and basic test Thomas Chou
2015-11-06 23:58     ` Simon Glass
2015-11-06  3:15   ` [U-Boot] [PATCH v2 1/2] common/board_f.c: move mark_bootstage after arch_cpu_init_dm Simon Glass
2015-11-06  4:08     ` Thomas Chou [this message]
2015-11-06 23:58       ` Simon Glass

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=563C27DA.3060106@wytron.com.tw \
    --to=thomas@wytron.com.tw \
    --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.