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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6D6C2C433EF for ; Thu, 21 Oct 2021 11:47:57 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 419F361208 for ; Thu, 21 Oct 2021 11:47:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230329AbhJULuM (ORCPT ); Thu, 21 Oct 2021 07:50:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57378 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229765AbhJULuL (ORCPT ); Thu, 21 Oct 2021 07:50:11 -0400 Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AE6BCC06174E for ; Thu, 21 Oct 2021 04:47:55 -0700 (PDT) Received: by mail-wr1-x429.google.com with SMTP id d3so608816wrh.8 for ; Thu, 21 Oct 2021 04:47:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=yBNHXGhEhbZK9RhqGx3nsWnlm7UlQUKLFmDxMWFI5UY=; b=bl2uLbPQUpuHGv4zy6LiqDvLjNFQBkpIMepHiGg3sWKGkaWY8LQO9hvtLlZZnrzc3I VIRckpn3xAw1bexg1E/DB/5fe/eAEIjAlDFvXq6InHqWhhcWuEOR7NJXIcTamWT/Zj4C 5hd6ATD2R1rkcjdmoCEqkWGGz1doci9FtZxdPWPtU1jg1/R3CFN3w9BrJ1jM5HT+ROeC F7tQ8VuGpgCBfQCOZlErx1GFMxiE7I4Rpe7FkOEwx9VXZr6OQeTjlPlEq4UeysT3GsEz 9eze1geDEfXw4/FjpG92oZvFes01FTKH2tD+Bz1gxVbuqa2qBb1/CBbQfBkeoRg0WkFL Fe3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=yBNHXGhEhbZK9RhqGx3nsWnlm7UlQUKLFmDxMWFI5UY=; b=KsvaT9Cwuy5UxfLbsrqkDJeC5EA6OZOpUy1/SuolYnhdIgoM3csFCG2WPppUZ/YR6z Qc+gFIOqzX/YJr+2tbE5jz7yuqmOSngGWAbhoOGAsSHpq0VkUi3mW7lJir8uYLQxHWsU WolhitVDYp7UXA9PL8aExNVNLOHz4clDNHwCI42TAlSCDWgW8Dw9q5nEInvqpjuRld/s 6f/yEIJYPLK8aVJsEzWXkv+m2wWvWG9NubltymnKh4wenPC1ikr3XctBu/6puRdEDe+U A1QMFtU4USNQlfP74INW6xt7dNq/QBOYtPWqjNcjQbbpJwzwx4kbD8QEoAV3iSHN8/LU m8nQ== X-Gm-Message-State: AOAM5338DcEe/63FydBeZ3BGMekra/Exx4BGClBubmayGXgLQfPQoesh eAPYx7UyBM39PBpFiqHg1Tc+aHb8Pyf87A== X-Google-Smtp-Source: ABdhPJxx0R+vs47hNv6vdLE3QmnjXyaLLPKRDSZGc9IS45STqa4yVBgZtFkZS2v0DcZyNcYqTW41RA== X-Received: by 2002:adf:d222:: with SMTP id k2mr6975449wrh.54.1634816874266; Thu, 21 Oct 2021 04:47:54 -0700 (PDT) Received: from google.com ([95.148.6.207]) by smtp.gmail.com with ESMTPSA id z1sm4579839wrt.94.2021.10.21.04.47.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 21 Oct 2021 04:47:53 -0700 (PDT) Date: Thu, 21 Oct 2021 12:47:52 +0100 From: Lee Jones To: Krzysztof Kozlowski Cc: Rob Herring , Chanwoo Choi , Bartlomiej Zolnierkiewicz , Liam Girdwood , Mark Brown , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 0/2] mfd/regulator: dt-bindings: max77686: convert to dtschema Message-ID: References: <20211008123552.191384-1-krzysztof.kozlowski@canonical.com> <85c56cfb-64d9-a840-c2e4-eea47461188d@canonical.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <85c56cfb-64d9-a840-c2e4-eea47461188d@canonical.com> Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Thu, 21 Oct 2021, Krzysztof Kozlowski wrote: > On 21/10/2021 12:03, Lee Jones wrote: > > On Fri, 08 Oct 2021, Krzysztof Kozlowski wrote: > > > >> Hi, > >> > >> Convert Maxim MAX77686 bindings to dtschema. The MFD patch (2/2) > >> depends on regulator, so this should go via one tree, for example MFD or DT. > >> > >> Changes since v1: > >> ================= > >> See individual patches. > >> > >> Clock bindings > >> ============== > >> Existing Documentation/devicetree/bindings/clock/maxim,max77686.txt are > >> left untouched. The file is still used/referenced by other Maxim > >> devices: MAX77620 and MAX77802. > >> > >> Best regards, > >> Krzysztof > >> > >> Krzysztof Kozlowski (2): > >> regulator: dt-bindings: maxim,max77686: convert to dtschema > >> dt-bindings: mfd: maxim,max77686: convert to dtschema > >> > >> .../devicetree/bindings/mfd/max77686.txt | 26 ---- > >> .../bindings/mfd/maxim,max77686.yaml | 132 ++++++++++++++++++ > >> .../bindings/regulator/max77686.txt | 71 ---------- > >> .../bindings/regulator/maxim,max77686.yaml | 83 +++++++++++ > >> MAINTAINERS | 2 +- > >> 5 files changed, 216 insertions(+), 98 deletions(-) > >> delete mode 100644 Documentation/devicetree/bindings/mfd/max77686.txt > >> create mode 100644 Documentation/devicetree/bindings/mfd/maxim,max77686.yaml > >> delete mode 100644 Documentation/devicetree/bindings/regulator/max77686.txt > >> create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max77686.yaml > > > > Does this need a PR too? > > No, I hope not. The regulator patch was acked by Mark and Rob, so you > can freely take both of these. I am not aware of any conflicts or other > dependencies. Acks do sometimes need PRs to be reciprocated. Just need to make sure. Mark, do you need a PR if I take this in via MFD? -- Lee Jones [李琼斯] Senior Technical Lead - Developer Services Linaro.org │ Open source software for Arm SoCs Follow Linaro: Facebook | Twitter | Blog