public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: hl <hl@rock-chips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 02/17] rockchip: move SYS_MALLOC_F_LEN to rk3288 own Kconfig
Date: Mon, 09 Nov 2015 10:59:35 +0800	[thread overview]
Message-ID: <56400C17.6070406@rock-chips.com> (raw)
In-Reply-To: <CAPnjgZ1MWfMaNp8crz2p9Xpg6uznhc7c4SLE6o4ie_YerH825g@mail.gmail.com>

Hi Simon,

On 06/11/15 20:08, Simon Glass wrote:
> Hi,
>
> On 6 November 2015 at 01:33, Lin Huang <hl@rock-chips.com> wrote:
>> since different rockchip SOC have different size of SRAM,
>> So the size SYS_MALLOC_F_LEN may different, so move this
>> config to rk3288 own Kconfig
>>
>> Signed-off-by: Lin Huang <hl@rock-chips.com>
>> ---
>> Changes in v1: None
>> Changes in v2: None
>> Changes in v3: None
>>
>>   arch/arm/mach-rockchip/Kconfig        | 3 ---
>>   arch/arm/mach-rockchip/rk3288/Kconfig | 3 +++
>>   2 files changed, 3 insertions(+), 3 deletions(-)
> I thought I Acked this patch, and several others. To avoid me having
> to review everything again, can you please pick those up and send a
> new version?
     i checked v1 patch,  you Ack several patchs, include:
      rockchip: Bring in RK3036 device tree file includes and bindings
      rockchip: rk3036: Add clock driver
      rockchip: rk3036: Add header files for GRF
      rockchip: rk3036: Add Soc reset driver
      rockchip: rk3036: Add a simple syscon driver
      rockchip: rk3036: Add pinctrl driver
     but since we add the SPL stage,  it is a big move, so these patchs 
all have been modified,
     and need your help to review again,
> Regards,
> Simon
>
>
>

-- 
Lin Huang

  reply	other threads:[~2015-11-09  2:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06  9:33 [U-Boot] [PATCH v3 00/20] Bring up rk3036 uboot Lin Huang
2015-11-06  9:33 ` [U-Boot] [PATCH v3 01/17] rockchip: add timer driver Lin Huang
2015-11-06  9:33 ` [U-Boot] [PATCH v3 02/17] rockchip: move SYS_MALLOC_F_LEN to rk3288 own Kconfig Lin Huang
2015-11-06 12:08   ` Simon Glass
2015-11-09  2:59     ` hl [this message]
2015-11-09  4:46       ` Simon Glass
2015-11-09  4:51         ` hl
2015-11-06  9:33 ` [U-Boot] [PATCH v3 03/17] rockchip: rename board-spl.c to rk3288-board-spl.c Lin Huang
2015-11-06  9:33 ` [U-Boot] [PATCH v3 04/17] rockchip: add config decide whether to build common.c Lin Huang
2015-11-06  9:33 ` [U-Boot] [PATCH v3 05/17] dm: core: Add SPL Kconfig for REGMAP and SYSCON Lin Huang
2015-11-06  9:33 ` [U-Boot] [PATCH v3 06/17] rockchip: serial driver support rk3036 Lin Huang
2015-11-06  9:33 ` [U-Boot] [PATCH v3 07/17] rockchip: Bring in RK3036 device tree file includes and bindings Lin Huang
2015-11-06  9:33 ` [U-Boot] [PATCH v3 08/17] rockchip: rk3036: Add clock driver Lin Huang
2015-11-06  9:33 ` [U-Boot] [PATCH v3 09/17] rockchip: rk3036: Add header files for GRF Lin Huang
2015-11-06  9:33 ` [U-Boot] [PATCH v3 10/17] rockchip: rk3036: Add Soc reset driver Lin Huang
2015-11-06  9:33 ` [U-Boot] [PATCH v3 11/17] rockchip: rk3036: Add a simple syscon driver Lin Huang
2015-11-06  9:33 ` [U-Boot] [PATCH v3 12/17] rockchip: rk3036: Add pinctrl driver Lin Huang
2015-11-06  9:33 ` [U-Boot] [PATCH v3 13/17] rockchip: Add an rk3036 MMC driver Lin Huang
2015-11-06  9:33 ` [U-Boot] [PATCH v3 14/17] rockchip: add early uart driver Lin Huang

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=56400C17.6070406@rock-chips.com \
    --to=hl@rock-chips.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