From: Simon Horman <horms@verge.net.au>
To: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 0/2] arm64: renesas: add H3ULCB board
Date: Thu, 11 Aug 2016 11:10:58 +0200 [thread overview]
Message-ID: <20160811091058.GI30475@verge.net.au> (raw)
In-Reply-To: <1469382353-14847-1-git-send-email-vladimir.barinov@cogentembedded.com>
Hi Vladimir,
On Sun, Jul 24, 2016 at 08:45:53PM +0300, Vladimir Barinov wrote:
> Hello,
>
> This adds the folowing:
> - R8A7795 SoC based H3ULCB low cost board initial device tree
> - Document DT bindings
In principle I am happy to with adding the H3ULCB to mainline but I am wondering
if you could make some adjustments to your patches so they fit the scheme
we usually use when adding new boards (and SoCs) to mainline.
Please split up the first patch as follows:
* A first patch which enables a very small subset of features:
- One CPU, some memory, a serial port, and anything else required
to boot to a rudimentary user-space.
- I am happy for you to post this by itself
* Then follow-up patches which one-by one enable SoC features such
as more CPUs, more memory, and of course more IP blocks (more serial
ports, SDHI, etc...)
Furthermore, if any of the SoC features you wish to enable are not already
enabled in mainline for the H3/Salvator-x then please arrange so they
appear at the end of the patchset or provided as a follow-up patchset
(possibly later).
prev parent reply other threads:[~2016-08-11 9:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-24 17:45 [PATCH v2 0/2] arm64: renesas: add H3ULCB board Vladimir Barinov
2016-07-24 17:46 ` [PATCH v2 1/2] arm64: renesas: h3ulcb: initial device tree Vladimir Barinov
2016-07-24 17:46 ` [PATCH v2 2/2] dt: arm: shmobile: add H3ULCB board DT bindings Vladimir Barinov
2016-07-26 19:09 ` Rob Herring
2016-08-25 10:09 ` Geert Uytterhoeven
2016-08-11 9:10 ` Simon Horman [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=20160811091058.GI30475@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=vladimir.barinov@cogentembedded.com \
/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