public inbox for linux-rockchip@lists.infradead.org
 help / color / mirror / Atom feed
From: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To: Jagan Teki <jagan@amarulasolutions.com>,
	Simon Glass <sjg@chromium.org>,
	Philipp Tomsich <philipp.tomsich@theobroma-systems.com>,
	Kever Yang <kever.yang@rock-chips.com>,
	Akash Gajjar <akash@openedev.com>, Tom Rini <trini@konsulko.com>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: linux-rockchip@lists.infradead.org,
	linux-amarula@amarulasolutions.com, u-boot@lists.denx.de
Subject: Re: [PATCH v6 0/3] arm64: rockchip: dts: Add rk3399 -u-boot.dtsi files
Date: Thu, 02 May 2019 09:43:57 +0200	[thread overview]
Message-ID: <b3dbf0578c96cf74ab5119e46f3dec5bcf406726.camel@bootlin.com> (raw)
In-Reply-To: <20190427114202.7358-1-jagan@amarulasolutions.com>

Hi,

On Sat, 2019-04-27 at 17:11 +0530, Jagan Teki wrote:
> This series is a rework of v5 patch that send it in separate series[1]
> 
> All these changes are creating an initial rk3399-u-boot.dtsi and rk3399
> board -u-boot.dtsi files and u-boot specific dts changes like
> - sdram dtsi
> - sdmmc, u-boot,dm-pre-reloc
> - spi1, u-boot,dm-pre-reloc

For the whole series:
Reviewed-by: Paul Kocialkowski <paul.kocialkowski@bootlin.com>

Cheers,

Paul

> Changes for v6:
> - spilt the existing patch[1] into multiple patches
>   and send as a separate series.
> 
> [1] https://patchwork.ozlabs.org/patch/1091720/
> 
> Any inputs?
> Jagan.
> 
> Jagan Teki (3):
>   arm64: rockchip: dts: rk3399: Add board -u-boot.dtsi files
>   arm64: rockchip: dts: Add initial rk3399-u-boot.dtsi file
>   arm64: rockchip: dts: rk3399: Use rk3399-u-boot.dtsi
> 
>  arch/arm/dts/rk3399-evb-u-boot.dtsi     |  7 +++++++
>  arch/arm/dts/rk3399-evb.dts             |  2 --
>  arch/arm/dts/rk3399-ficus-u-boot.dtsi   |  6 ++++++
>  arch/arm/dts/rk3399-ficus.dts           |  1 -
>  arch/arm/dts/rk3399-firefly-u-boot.dtsi |  7 +++++++
>  arch/arm/dts/rk3399-firefly.dts         |  2 --
>  arch/arm/dts/rk3399-gru-bob-u-boot.dtsi |  7 +++++++
>  arch/arm/dts/rk3399-gru-bob.dts         |  1 -
>  arch/arm/dts/rk3399-gru-u-boot.dtsi     |  6 ++++++
>  arch/arm/dts/rk3399-gru.dtsi            |  1 -
>  arch/arm/dts/rk3399-puma-ddr1600.dts    |  1 +
>  arch/arm/dts/rk3399-puma.dtsi           |  3 ---
>  arch/arm/dts/rk3399-rock960-u-boot.dtsi |  6 ++++++
>  arch/arm/dts/rk3399-rock960.dts         |  1 -
>  arch/arm/dts/rk3399-u-boot.dtsi         | 12 ++++++++++++
>  15 files changed, 52 insertions(+), 11 deletions(-)
>  create mode 100644 arch/arm/dts/rk3399-evb-u-boot.dtsi
>  create mode 100644 arch/arm/dts/rk3399-ficus-u-boot.dtsi
>  create mode 100644 arch/arm/dts/rk3399-firefly-u-boot.dtsi
>  create mode 100644 arch/arm/dts/rk3399-gru-bob-u-boot.dtsi
>  create mode 100644 arch/arm/dts/rk3399-gru-u-boot.dtsi
>  create mode 100644 arch/arm/dts/rk3399-rock960-u-boot.dtsi
>  create mode 100644 arch/arm/dts/rk3399-u-boot.dtsi
> 
-- 
Paul Kocialkowski, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

      parent reply	other threads:[~2019-05-02  7:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-27 11:41 [PATCH v6 0/3] arm64: rockchip: dts: Add rk3399 -u-boot.dtsi files Jagan Teki
     [not found] ` <20190427114202.7358-1-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2019-04-27 11:42   ` [PATCH v6 1/3] arm64: rockchip: dts: rk3399: Add board " Jagan Teki
2019-04-27 11:42   ` [PATCH v6 2/3] arm64: rockchip: dts: Add initial rk3399-u-boot.dtsi file Jagan Teki
2019-04-27 11:42   ` [PATCH v6 3/3] arm64: rockchip: dts: rk3399: Use rk3399-u-boot.dtsi Jagan Teki
2019-05-02  7:43 ` Paul Kocialkowski [this message]

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=b3dbf0578c96cf74ab5119e46f3dec5bcf406726.camel@bootlin.com \
    --to=paul.kocialkowski@bootlin.com \
    --cc=akash@openedev.com \
    --cc=jagan@amarulasolutions.com \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=philipp.tomsich@theobroma-systems.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.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