From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: dts: rockchip: Enable build of rk3066 MK808 dts
Date: Thu, 06 Oct 2016 18:33:13 +0200 [thread overview]
Message-ID: <46121446.zsYkG9qnut@phil> (raw)
In-Reply-To: <84d4bc0b733cb9776f03ad54bb946fd1c4be4049.1475764778.git.paweljarosz3691@gmail.com>
Hi Pawe?,
Am Donnerstag, 6. Oktober 2016, 18:22:40 CEST schrieb =?UTF-8?q?
Pawe=C5=82=20Jarosz?=:
> MK808 is rockchip rk3066 based board made by Rickomagic. It has two usb
> ports, sdmmc, wifi and uart onboard.
>
> Signed-off-by: Pawe? Jarosz <paweljarosz3691@gmail.com>
> ---
> arch/arm/boot/dts/Makefile | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
> index befcd26..f19cc1d 100644
> --- a/arch/arm/boot/dts/Makefile
> +++ b/arch/arm/boot/dts/Makefile
> @@ -639,6 +639,7 @@ dtb-$(CONFIG_ARCH_ROCKCHIP) += \
> rk3036-kylin.dtb \
> rk3066a-bqcurie2.dtb \
> rk3066a-marsboard.dtb \
> + rk3066a-mk808.dtb \
> rk3066a-rayeager.dtb \
> rk3188-radxarock.dtb \
> rk3228-evb.dtb \
This patch breaks bisectability, as it adds a dtb to the makefile that you only
add in patch3 which makes builds fail. Please fold your patches 1 and 3 into
one patch and also add and entry to Documentation/devicetree/bindings/arm/
rockchip.txt for the board.
Heiko
next prev parent reply other threads:[~2016-10-06 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 16:22 [PATCH 0/3] Add MK808 RK3066 device =?UTF-8?q?Pawe=C5=82=20Jarosz?=
2016-10-06 16:22 ` [PATCH 1/3] ARM: dts: rockchip: Enable build of rk3066 MK808 dts =?UTF-8?q?Pawe=C5=82=20Jarosz?=
2016-10-06 16:33 ` Heiko Stuebner [this message]
2016-10-06 17:05 ` Paweł Jarosz
2016-10-06 17:05 ` Heiko Stuebner
2016-10-06 16:23 ` [PATCH 2/3] devicetree: Add vendor prefix for Rikomagic =?UTF-8?q?Pawe=C5=82=20Jarosz?=
2016-10-06 16:23 ` [PATCH 3/3] ARM: dts: rockchip: Add rk3066 MK808 board devicetree description file =?UTF-8?q?Pawe=C5=82=20Jarosz?=
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=46121446.zsYkG9qnut@phil \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).