From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
Thomas Gleixner <tglx@linutronix.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v2 1/3] dt-bindings: timer: renesas, cmt: Document r8a774[35] CMT support
Date: Thu, 25 Jan 2018 09:35:17 +0100 [thread overview]
Message-ID: <bf1b052d-c8e1-49dc-9e62-13d564d223a4@linaro.org> (raw)
In-Reply-To: <CAMuHMdUX8D6c_ehNJAS8nWprvY60bkoxwTekEEqT5oJcz4QGPA@mail.gmail.com>
On 25/01/2018 09:21, Geert Uytterhoeven wrote:
> Hi Daniel,
>
> On Thu, Jan 25, 2018 at 9:09 AM, Daniel Lezcano
> <daniel.lezcano@linaro.org> wrote:
>> On 24/01/2018 17:49, Fabrizio Castro wrote:
>>> I am sorry to bother you, just wondering if you think there are any chances for this patch to applied on top of v4.16?
>>
>> You can take it through the renesas tree.
>>
>> Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>
> Thank you!
>
> Unfortunately it's a bit late to get non-bugfixes in v4.16 through the renesas
> tree and arm-soc.
I thought they were going through the renesas tree, so I discarded them :/
May be Thomas can take them in the tip/timers tree ?
Thomas ?
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2018-01-25 8:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 17:39 [PATCH v2 0/3] Add CMT support to r8a774[35] Fabrizio Castro
[not found] ` <1513618743-4773-1-git-send-email-fabrizio.castro-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org>
2017-12-18 17:39 ` [PATCH v2 1/3] dt-bindings: timer: renesas, cmt: Document r8a774[35] CMT support Fabrizio Castro
2018-01-24 16:49 ` Fabrizio Castro
[not found] ` <SG2PR06MB088625944BCD8F4307315520C0E20-ESzmfEwOt/zNWVFMfLWNqm0DtJ1/0DrXvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-01-25 8:09 ` Daniel Lezcano
2018-01-25 8:21 ` Geert Uytterhoeven
2018-01-25 8:35 ` Daniel Lezcano [this message]
2018-03-06 16:21 ` Fabrizio Castro
2018-04-10 9:36 ` Fabrizio Castro
2018-05-13 7:47 ` Simon Horman
2018-05-15 9:35 ` Fabrizio Castro
2017-12-18 17:39 ` [PATCH v2 2/3] ARM: dts: r8a7743: Add CMT SoC specific support Fabrizio Castro
[not found] ` <1513618743-4773-3-git-send-email-fabrizio.castro-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org>
2017-12-19 11:20 ` Geert Uytterhoeven
2017-12-20 9:13 ` Simon Horman
2017-12-18 17:39 ` [PATCH v2 3/3] ARM: dts: r8a7745: " Fabrizio Castro
2017-12-19 11:21 ` Geert Uytterhoeven
2017-12-20 9:24 ` 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=bf1b052d-c8e1-49dc-9e62-13d564d223a4@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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).