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 D0922C433EF for ; Mon, 6 Jun 2022 15:37:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240932AbiFFPhn (ORCPT ); Mon, 6 Jun 2022 11:37:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54796 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240925AbiFFPhm (ORCPT ); Mon, 6 Jun 2022 11:37:42 -0400 Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D994C20BD8 for ; Mon, 6 Jun 2022 08:37:40 -0700 (PDT) Received: by mail-ej1-x62f.google.com with SMTP id me5so29192311ejb.2 for ; Mon, 06 Jun 2022 08:37:40 -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=TPOApYvb6Wxwe5KarWLI1DK2xlnELfMdmLjwPBhUFmY=; b=xrtvxq07G0Balt8gqFW0xfBnb/KqOGRnSXQmweTC1TqHRtRmMB5Bh3SvoaPCjDVZAl P/aPuE1HqZbPccP4zpOozDQ9Gq9/m5EvyK7WlkVZX4c1s9eK/NG2S3AjSAcEIOfVOjaQ 736slRtSeLnDfPGFQLrS1Fqyv3hmnkGTRWxg+UIjmMUXXCP13AIhHnFlGyJBerj6kcUn 05eA8tuaZvVdnTvXm0Q9jc20DHMXiNmttyvKF6udj6REH04kfJ/lUQAMRvhTIsumMwlM IH+2UF009KRW9/MJSIKfUEiw++VZFKtsS3FSjqjUZHETbMSyq8CkbvciVrO3ki2IhNZJ 1reQ== 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=TPOApYvb6Wxwe5KarWLI1DK2xlnELfMdmLjwPBhUFmY=; b=Jz+GYrBeXPoj695Zvb/3lygfpLuvUsnF0YG3GdwcSYGUYINX3K7gr1VdGhwTXebKhQ 3shmDZIxsqkHSToISZj0HtWYpPTeLbXbdaz9xl33c/C2rXQplntvIah7VU+uNS+dQGIG 7Je/H2gyGHwCGFRe5EPyYsNlDGqx6MzdRxRX6njMDmhupeD6BygIleI02mdL1BdSpqhP mK4PJ1mZBXj/Iv+NgZHS2l7/IFkFVj/JEbsmz4FLi/Edjt1ugIRJckqzNmrw2GS9aVhC g+tyUzK5Ifdk+AY+ZSlQd4yUt2WhRSZ2qGhL372Kwj2AeN9YaPw8yy+ZXDvKlYNC7VhQ Tuiw== X-Gm-Message-State: AOAM530j2cCjDTw5A0Rb8BoTlKbeQKnJA86/n7b0NtvmN8BHTt2I9YyT Vc5Z/5T3H2Qgo99Fo5yq/Ps5pQ== X-Google-Smtp-Source: ABdhPJyTldoWxgNbTyUfoG0DE5atMlvTxvy7y3jeS4TIndwvgOwStVK1T0DxwBIHX1tbTfm5woE5lw== X-Received: by 2002:a17:907:724a:b0:6ff:2ed0:960 with SMTP id ds10-20020a170907724a00b006ff2ed00960mr22376130ejc.480.1654529859405; Mon, 06 Jun 2022 08:37:39 -0700 (PDT) Received: from [192.168.0.181] (xdsl-188-155-176-92.adslplus.ch. [188.155.176.92]) by smtp.gmail.com with ESMTPSA id e26-20020a1709062c1a00b00711d88ae162sm669769ejh.24.2022.06.06.08.37.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 06 Jun 2022 08:37:38 -0700 (PDT) Message-ID: <8bd4323e-9005-6a15-b94b-c49427fffa68@linaro.org> Date: Mon, 6 Jun 2022 17:37:38 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: [PATCH 19/23] MAINTAINERS: update maxim,max77693.yaml reference Content-Language: en-US To: Mauro Carvalho Chehab , Linux Doc Mailing List , Jonathan Corbet Cc: Mauro Carvalho Chehab , Lee Jones , Rob Herring , linux-kernel@vger.kernel.org References: <6a87dfb278765465d82ad4641a42ae4de0ded392.1654529011.git.mchehab@kernel.org> From: Krzysztof Kozlowski In-Reply-To: <6a87dfb278765465d82ad4641a42ae4de0ded392.1654529011.git.mchehab@kernel.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On 06/06/2022 17:25, Mauro Carvalho Chehab wrote: > Changeset b38213c6118b ("dt-bindings: mfd: maxim,max77693: Convert to dtschema") > renamed: Documentation/devicetree/bindings/mfd/max77693.txt > to: Documentation/devicetree/bindings/mfd/maxim,max77693.yaml. > > Update its cross-reference accordingly. > > Fixes: b38213c6118b ("dt-bindings: mfd: maxim,max77693: Convert to dtschema") I look at that commit and it performs proper update of Maintainers file. It is not the commit which introduced the issue, so the fixes tag is wrong. The commit which introduced the issue is I think within Lee's branches: Fixes: afb67df31a8c ("Merge branches 'ib-mfd-hwmon-regulator-5.18', 'ib-mfd-iio-5.18', 'ib-mfd-led-power-regulator-5.18', 'ib-mfd-mediatek-mt6366-5.18', 'ib-mfd-rtc-watchdog-5.18' and 'ib-mfd-spi-dt-5.18' into ibs-for-mfd-merged") > Signed-off-by: Mauro Carvalho Chehab > --- > > To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. > See [PATCH 00/23] at: https://lore.kernel.org/all/cover.1654529011.git.mchehab@kernel.org/ > > MAINTAINERS | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/MAINTAINERS b/MAINTAINERS > index a11aa7ebb6af..dc64a23d0bdc 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -12118,7 +12118,7 @@ F: Documentation/devicetree/bindings/*/maxim,max77686.yaml > F: Documentation/devicetree/bindings/*/maxim,max77693.yaml > F: Documentation/devicetree/bindings/*/maxim,max77843.yaml > F: Documentation/devicetree/bindings/clock/maxim,max77686.txt > -F: Documentation/devicetree/bindings/mfd/max77693.txt > +F: Documentation/devicetree/bindings/mfd/maxim,max77693.yaml This "+" is not correct. The entry is already properly covered. Just remove the max77693.txt. Best regards, Krzysztof