From: Matthias Brugger <matthias.bgg@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: wim@iguana.be, linux@roeck-us.net, mark.rutland@arm.com,
catalin.marinas@arm.com, will.deacon@arm.com,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Matthias Brugger <mbrugger@suse.com>
Subject: Re: [PATCH 1/4] ARM: mediatek: dts: Cleanup bindings documentation
Date: Tue, 1 Aug 2017 15:44:06 +0200 [thread overview]
Message-ID: <5451bdfa-e2c1-30cb-a5a9-252662b2d190@gmail.com> (raw)
In-Reply-To: <20170724195644.oztdexqhicir5xn3@rob-hp-laptop>
On 07/24/2017 09:56 PM, Rob Herring wrote:
> On Thu, Jul 20, 2017 at 12:22:44PM +0200, Matthias Brugger wrote:
>> From: Matthias Brugger <mbrugger@suse.com>
>>
>> This patch cleans up the binding documentation stating explicitly
>> the binding and it's fallback for every SoC.
>>
>> Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
>> ---
>> Documentation/devicetree/bindings/watchdog/mtk-wdt.txt | 5 ++---
>> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> Acked-by: Rob Herring <robh@kernel.org>
>
Thanks. Whole series pushed now to v4.13-next/dts64
prev parent reply other threads:[~2017-08-01 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 10:22 [PATCH 1/4] ARM: mediatek: dts: Cleanup bindings documentation Matthias Brugger
2017-07-20 10:22 ` [PATCH 2/4] ARM: mediatek: dts: Add mt6796 binding Matthias Brugger
2017-07-24 19:57 ` Rob Herring
2017-07-20 10:22 ` [PATCH 3/4] arm64: dts: mediatek: add watchdog to MT6796 Matthias Brugger
2017-07-20 10:22 ` [PATCH 4/4] arm64: dts: mediatek: Delete unused dummy clock for MT6797 Matthias Brugger
2017-07-24 19:56 ` [PATCH 1/4] ARM: mediatek: dts: Cleanup bindings documentation Rob Herring
2017-08-01 13:44 ` Matthias Brugger [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=5451bdfa-e2c1-30cb-a5a9-252662b2d190@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=mbrugger@suse.com \
--cc=robh@kernel.org \
--cc=will.deacon@arm.com \
--cc=wim@iguana.be \
/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