From: kieran@bingham.xyz (Kieran Bingham)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] arm64: dts: r8a7795: FCPF and FDP1 device nodes
Date: Thu, 30 Jun 2016 14:32:41 +0100 [thread overview]
Message-ID: <1467293563-940-1-git-send-email-kieran@bingham.xyz> (raw)
Hi Simon,
Here is my updated series for the dts updates in relation to the RCar/FDP1.
The fcpf patch has collected a reviewed-by from Geert, whilst the fdp1
patch has collected a reviewed by from both Laurent and Geert, with a
small change to remove the labels, as they will not be referenced.
You responded to my previous set for these with the following comment:
> These patches look good to me. My assumption is that they
> can be applied without causing any breakage and that the
> relevant features will start working once driver support
> shows up in the kernel.
>
> If the above assumption is correct then please let me know when the
> bindings have been accepted by the relevant subsystem maintainer(s).
>
> If the patches need rebasing at that time then please repost them.
> Otherwise you can either repost them or ping me as a response to this thread.
Your assumption was correct, and they could be applied without breakage.
RobH has acked the binding for the RCar FCPF, but I have not seen an ack for
the FDP1 binding yet. I'll follow that up, and ping you on the fdp1 dts patch
when it resolved.
Regards
Kieran
--
Kieran Bingham (2):
arm64: dts: r8a7795: add FCPF device nodes
arm64: dts: r8a7795: add FDP1 device nodes
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 48 ++++++++++++++++++++++++++++++++
1 file changed, 48 insertions(+)
--
2.7.4
next reply other threads:[~2016-06-30 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 13:32 Kieran Bingham [this message]
2016-06-30 13:32 ` [PATCH 1/2] arm64: dts: r8a7795: add FCPF device nodes Kieran Bingham
2016-06-30 13:32 ` [PATCH 2/2] arm64: dts: r8a7795: add FDP1 " Kieran Bingham
2016-07-01 14:37 ` Kieran Bingham
2016-07-04 12:45 ` Simon Horman
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=1467293563-940-1-git-send-email-kieran@bingham.xyz \
--to=kieran@bingham.xyz \
--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).