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 5D9A8ECAAD5 for ; Tue, 30 Aug 2022 18:43:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231540AbiH3Snn (ORCPT ); Tue, 30 Aug 2022 14:43:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50940 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231512AbiH3Snk (ORCPT ); Tue, 30 Aug 2022 14:43:40 -0400 Received: from mail-oa1-f49.google.com (mail-oa1-f49.google.com [209.85.160.49]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 11DBB719AE for ; Tue, 30 Aug 2022 11:43:36 -0700 (PDT) Received: by mail-oa1-f49.google.com with SMTP id 586e51a60fabf-11edd61a9edso12833364fac.5 for ; Tue, 30 Aug 2022 11:43:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc; bh=rSGqIKaWJx4R4bUfe0Omf0nrWxdjC071wJDzr6SYEFI=; b=PH0dR6JI1yvkhefPYJCGhxJC97nvLNrgudnXISflhOMAi6yz/+YIYv+lz6MlOqNbUc iA0Ym1erOIb67dNfYaunrdDcMrrf2Hn7MK7RaLI1WPCrN7XlL1euFCREIKNIc8QA1jgA +eU1nO13lz4nMJD6i7sgS/Ocll+m5DrC46xkWc7anr3h9UJ424ZF/PFTUtFenrHnsFPz lr/Weu7SqCj6LZnPnt1k2oePoDrACncPXmt4FhFi6sPL9gpF/EPUtEU4kND1Q76HQEGd WENpL2sSBz/mxb9JCJysfron95LR0CX47jfXtF4/XYn5b7OiSkyYjzmZsGRY2wR4HQqA /t6g== X-Gm-Message-State: ACgBeo1jVe3DITmsqz1ZA3bH6oXY9wPdPicDJcgVWtWbBPT+7LJXRTCY rkS+HpOWQwDoCvpKXaIoFxOYKPAZ7A== X-Google-Smtp-Source: AA6agR7uAW/qGHnJ6m4c1HGT0W3p1Ka1MuJUbTlEBrrjv+gY1LC7B5ZqVjhM9w26tSsZbZnXlI46fg== X-Received: by 2002:a05:6870:8890:b0:101:db34:3ed6 with SMTP id m16-20020a056870889000b00101db343ed6mr11345946oam.151.1661885015371; Tue, 30 Aug 2022 11:43:35 -0700 (PDT) Received: from robh.at.kernel.org (66-90-144-107.dyn.grandenetworks.net. [66.90.144.107]) by smtp.gmail.com with ESMTPSA id s2-20020a4aeac2000000b0044884c40c8asm7033999ooh.30.2022.08.30.11.43.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 30 Aug 2022 11:43:35 -0700 (PDT) Received: (nullmailer pid 1836908 invoked by uid 1000); Tue, 30 Aug 2022 18:43:34 -0000 Date: Tue, 30 Aug 2022 13:43:34 -0500 From: Rob Herring To: Andrew Lunn Cc: Gregory Clement , arm-soc , Device Tree Subject: Re: [PATCH v2 00/12] Start converting MVEBU bindings to DT Schema Message-ID: <20220830184334.GA1825505-robh@kernel.org> References: <20220825013258.3459714-1-andrew@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220825013258.3459714-1-andrew@lunn.ch> Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Thu, Aug 25, 2022 at 03:32:46AM +0200, Andrew Lunn wrote: > This is the first batch of patches converting the Marvell MVEBU driver > bindings from .txt to .yaml. So far, kirkwood has been used for > testing, but these drivers apply to a range of Marvell SoCs. > > In order to reduce the number of warnings from the DT schema checking > tools, a few minor changes have been made to a few DT files. No actual > errors have been found, the changes just make the checker quiet. > > I propose these patches are merged via mvebu to arm-soc. No conflicts > are expected with these patches. Why? I strongly prefer the bindings go via subsystem trees. That is the documented way. As pointed out in v1, you again have not Cc'ed the subsystem maintainers. Please resend. Rob