From: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
To: Simon Horman <horms@verge.net.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Magnus Damm <magnus.damm@gmail.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
"xu_shunji@hoperun.com" <xu_shunji@hoperun.com>
Subject: RE: [PATCH] arm64: dts: renesas: hihope-common: Add LEDs support
Date: Wed, 19 Jun 2019 14:11:41 +0000 [thread overview]
Message-ID: <TY1PR01MB177099A8BAF4B364AAE8A780C0E50@TY1PR01MB1770.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20190619121808.hnqoeihjch6silcd@verge.net.au>
Hello Simon,
> From: Simon Horman <horms@verge.net.au>
> Sent: 19 June 2019 13:18
> Subject: Re: [PATCH] arm64: dts: renesas: hihope-common: Add LEDs support
>
> >
> > Will do. Simon, do you want me to send an incremental patch for this (this patch
> > is on devel branch already) or would you rather I sent a v2?
>
> Please send an incremental patch, thanks.
Great, will send the patch in a minute.
Thanks,
Fab
prev parent reply other threads:[~2019-06-19 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 13:14 [PATCH] arm64: dts: renesas: hihope-common: Add LEDs support Fabrizio Castro
2019-06-17 9:33 ` Simon Horman
2019-06-18 10:40 ` Simon Horman
2019-06-18 15:10 ` Geert Uytterhoeven
2019-06-18 15:56 ` Fabrizio Castro
2019-06-19 7:33 ` Geert Uytterhoeven
2019-06-19 8:16 ` Fabrizio Castro
2019-06-19 12:18 ` Simon Horman
2019-06-19 14:11 ` Fabrizio Castro [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=TY1PR01MB177099A8BAF4B364AAE8A780C0E50@TY1PR01MB1770.jpnprd01.prod.outlook.com \
--to=fabrizio.castro@bp.renesas.com \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=xu_shunji@hoperun.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;
as well as URLs for NNTP newsgroup(s).