From: Matthias Brugger <matthias.bgg@gmail.com>
To: Rob Herring <robh@kernel.org>, arm@kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] dt-bindings: arm: Convert MediaTek board/soc bindings to json-schema
Date: Sat, 15 Jun 2019 12:17:57 +0200 [thread overview]
Message-ID: <8e4fcd7c-c698-7fe0-fce6-7f153112d16e@gmail.com> (raw)
In-Reply-To: <20190613224921.GA9199@bogus>
On 14/06/2019 00:49, Rob Herring wrote:
> On Fri, May 17, 2019 at 10:42:02AM -0500, Rob Herring wrote:
>> Convert MediaTek SoC bindings to DT schema format using json-schema.
>>
>> Cc: Mark Rutland <mark.rutland@arm.com>
>> Cc: Matthias Brugger <matthias.bgg@gmail.com>
>> Cc: devicetree@vger.kernel.org
>> Cc: linux-arm-kernel@lists.infradead.org
>> Cc: linux-mediatek@lists.infradead.org
>> Signed-off-by: Rob Herring <robh@kernel.org>
>> ---
>> v3:
>> - Rebase to Linus' master
>>
>> .../devicetree/bindings/arm/mediatek.txt | 89 ------------------
>> .../devicetree/bindings/arm/mediatek.yaml | 91 +++++++++++++++++++
>> 2 files changed, 91 insertions(+), 89 deletions(-)
>> delete mode 100644 Documentation/devicetree/bindings/arm/mediatek.txt
>> create mode 100644 Documentation/devicetree/bindings/arm/mediatek.yaml
>
> Ping. Three versions of this and no comments... Is Mediatek a dead
> platform?
>
No just a too busy maintainer. Somehow I remembered that you mentioned you won't
rebase it, so I put it on my long list of todos.
Pushed now to v5.2-next/dts64
Thanks a lot!
Matthias
prev parent reply other threads:[~2019-06-15 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 15:42 [PATCH v3] dt-bindings: arm: Convert MediaTek board/soc bindings to json-schema Rob Herring
2019-06-13 22:49 ` Rob Herring
2019-06-15 10:17 ` 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=8e4fcd7c-c698-7fe0-fce6-7f153112d16e@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=arm@kernel.org \
--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=mark.rutland@arm.com \
--cc=robh@kernel.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).