devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Andy Yan <andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
	afaerber-l3A5Bk7waGM@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v1 1/2] ARM: dts: add rockchip PX3 Evaluation board
Date: Tue, 13 Sep 2016 13:04:25 +0200	[thread overview]
Message-ID: <1473786122.FM2XgiQb2U@phil> (raw)
In-Reply-To: <94379f31-00bb-4873-5a93-f6eeead55180-TNX95d0MmH7DzftRWevZcw@public.gmane.org>

Hi Andy,

Am Dienstag, 13. September 2016, 18:06:12 CEST schrieb Andy Yan:
> Hi Heiko:
> 
>      Is there any further suggestion about this series?

nope, all fine. I've now applied both patches, after moving some minor stuff
around (alphabetical ordering etc). While it is in branches targeted at 4.9 it
may very well only make it into 4.10.

I've also dropped the stk3310 i2c node from both until the binding is figured
out and moved the px3 board binding to the px5 patch, so that we can sort
entries correctly but don't produce merge conflicts.

If you have time, please give it a final look:
https://git.kernel.org/cgit/linux/kernel/git/mmind/linux-rockchip.git/commit/?id=a55e2f1b7423ab8b1c3fefbac7ae752e8a4b7edc
https://git.kernel.org/cgit/linux/kernel/git/mmind/linux-rockchip.git/commit/?id=d42f818e056116237ac8b6a3f72e5bfc38681589


Heiko
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-09-13 11:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-10 17:40 [PATCH v1 0/2] Add two automotive field Evaluation boards from rockchip Andy Yan
     [not found] ` <1473529249-6151-1-git-send-email-andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-09-10 17:44   ` [PATCH v1 1/2] ARM: dts: add rockchip PX3 Evaluation board Andy Yan
2016-09-13 10:06     ` Andy Yan
     [not found]       ` <94379f31-00bb-4873-5a93-f6eeead55180-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-09-13 11:04         ` Heiko Stuebner [this message]
2016-09-13 12:14     ` Andreas Färber
     [not found]       ` <64f4be31-1b19-60e3-da7c-f2fec186fab9-l3A5Bk7waGM@public.gmane.org>
2016-10-10  9:54         ` Heiko Stuebner
2016-10-10 11:25           ` Andy Yan
2016-09-10 17:47   ` [PATCH v1 2/2] arm64: dts: rockchip: Add PX5 " Andy Yan
     [not found]     ` <1473529623-6268-1-git-send-email-andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-09-13 12:23       ` Andreas Färber
2016-10-10 12:23         ` Heiko Stuebner

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=1473786122.FM2XgiQb2U@phil \
    --to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
    --cc=afaerber-l3A5Bk7waGM@public.gmane.org \
    --cc=andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
    --cc=briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).