From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7BBB1C43219 for ; Mon, 18 Apr 2022 11:41:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236394AbiDRLoZ (ORCPT ); Mon, 18 Apr 2022 07:44:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48784 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232287AbiDRLoY (ORCPT ); Mon, 18 Apr 2022 07:44:24 -0400 Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8328E12AF6 for ; Mon, 18 Apr 2022 04:41:45 -0700 (PDT) Received: by mail-ed1-x536.google.com with SMTP id z12so17175025edl.2 for ; Mon, 18 Apr 2022 04:41:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=fmqrWEaMLzdzM6tlfO27gc/5ZjxaVbLantgCWtrzxek=; b=euLeyub8VKd1us4OwhWIZzr3XV+POZ9D4tQLxC59vh85fmzN0/EVt8PiyZEOcOThP2 SGipuK3/fFUQh4OIEj/tUPjKfgC4U1Vs1JR44X8fEktdAUef0FmXFVAl9yS7wlBCamz4 1FNGh7HdJJdtqnUyE/EwU5nAlurUZzRIx+/YyEtGXFLtc7RrKS8kr6hBSnkxpVmQLGTB quVtKz+eAR+F22D8M88AXByTb73Ytb3RUid038sU3fozUZAFcsUs0QcL+n4RZla9hT+7 br9Rd0/8aWonrhkRGsDF/ng25tJ4WSiZn7AJbj6hxM4rzWzfFznwcs1jpby8AxAizWLl 9K8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=fmqrWEaMLzdzM6tlfO27gc/5ZjxaVbLantgCWtrzxek=; b=iNko0XSPXkXhw4L0gGlbV0MYDRl8i6cZG5OKlFD2iIlZ19EIVsxDz9T5ICv2bObQ4w WH3YFX0RNdP8cDNh1rS63Rs9nYkg5pEjHFU7fueEQaTIH8FuxYUeNu3R4M5ntTApZHLp /33PJ6V8LLYiZalv3wCH0kui2/eP8cTqOKBGyrC/daMqtCR5jz7JDSjUJ2IRfBeDXo5W kIKS8/gagHsjL/4QKWBf1d0tyk8zroqgQoC2pVNrk+uCSGxoNISoUhwOZVzYoIGWDTjA MTryUHrzOIIEpMJtE6utnRoh6EIOBHEBZp2J4JZoGTmgrweuTwBPnEAgMm0Vnaric3dB AaWA== X-Gm-Message-State: AOAM532lbeu8yhuRLGPFOLHiuWeH/wuDdqMvhsMTO27XgEWFDW7Gxcvq xmYAZd5h6JlnDuYJa+0ilu6JyQ== X-Google-Smtp-Source: ABdhPJy5kGTGP7Apl58/+o1/q/TVZVuRIYgAiCuDaaJBGKYub7vpPI4igucgaDqIEtBRy96pV5HUgQ== X-Received: by 2002:aa7:c68d:0:b0:41d:7b1c:7da0 with SMTP id n13-20020aa7c68d000000b0041d7b1c7da0mr11742036edq.175.1650282104090; Mon, 18 Apr 2022 04:41:44 -0700 (PDT) Received: from [192.168.0.217] (xdsl-188-155-176-92.adslplus.ch. [188.155.176.92]) by smtp.gmail.com with ESMTPSA id u25-20020a170906b11900b006e08588afedsm4506051ejy.132.2022.04.18.04.41.42 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 18 Apr 2022 04:41:43 -0700 (PDT) Message-ID: <09df1d1f-71cf-a24f-2908-8e1630d9c536@linaro.org> Date: Mon, 18 Apr 2022 13:41:42 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: [PATCH 3/4] dt-bindings: mmc: convert orion-sdio to JSON schema Content-Language: en-US To: Chris Packham , ulf.hansson@linaro.org, robh+dt@kernel.org, krzk+dt@kernel.org, andrew@lunn.ch, gregory.clement@bootlin.com, sebastian.hesselbarth@gmail.com Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org References: <20220414230603.567049-1-chris.packham@alliedtelesis.co.nz> <20220414230603.567049-4-chris.packham@alliedtelesis.co.nz> From: Krzysztof Kozlowski In-Reply-To: <20220414230603.567049-4-chris.packham@alliedtelesis.co.nz> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 15/04/2022 01:06, Chris Packham wrote: > Convert the orion-sdio binding to JSON schema. > > Signed-off-by: Chris Packham > --- > .../bindings/mmc/marvell,orion-sdio.yaml | 43 +++++++++++++++++++ > .../devicetree/bindings/mmc/orion-sdio.txt | 16 ------- > 2 files changed, 43 insertions(+), 16 deletions(-) > create mode 100644 Documentation/devicetree/bindings/mmc/marvell,orion-sdio.yaml > delete mode 100644 Documentation/devicetree/bindings/mmc/orion-sdio.txt > > diff --git a/Documentation/devicetree/bindings/mmc/marvell,orion-sdio.yaml b/Documentation/devicetree/bindings/mmc/marvell,orion-sdio.yaml > new file mode 100644 > index 000000000000..4fef53fc78ed > --- /dev/null > +++ b/Documentation/devicetree/bindings/mmc/marvell,orion-sdio.yaml > @@ -0,0 +1,43 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/mmc/marvell,orion-sdio.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Marvell orion-sdio controller > + > +maintainers: > + - Ulf Hansson This should be someone having taking care about this hardware, not subsystem maintainer. If there is no dedicated person for Marvell MMC, then maybe SoC maintainers? Reviewed-by: Krzysztof Kozlowski Best regards, Krzysztof