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 B8794C433FE for ; Sat, 9 Apr 2022 13:27:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242006AbiDIN3F (ORCPT ); Sat, 9 Apr 2022 09:29:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41098 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242214AbiDIN2A (ORCPT ); Sat, 9 Apr 2022 09:28:00 -0400 Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9125BBF30D for ; Sat, 9 Apr 2022 06:24:52 -0700 (PDT) Received: by mail-ed1-x52b.google.com with SMTP id c64so793923edf.11 for ; Sat, 09 Apr 2022 06:24:52 -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=fDcvYkIEVq0f5BjuAYxIIri1A/cHLRrOx9YyUXqMPAI=; b=UawB3WzU+FxwrZ0kFUke+Bm5I2fHVYUC0ogGFxCbj94TVJljWRaz0NDT5A7zTtAUZP fw8JHjOxm0qDf1SFRI97P2JQv88wFOu2m9eUaHnYpkfvpZ25Rvb4FAMqI14CNSdAjI0q MchM+RmS9n5ye2oDsJq58sV+qzk6fsAb7jzr2e4SvyCyBgoCRj4qEEcZZJWfJkv24jHM RLCIy70bXWocIqk0Ww1n3bzsMfnl5U3iEJa6RmO6EmtvJN+P+HdPPAewAKhfBkB9OdPi ypoMSsTJBzRCut4Tt2V/nUtglORaWD2g+yPw4BTVrKPG/Ir3Rfaxnpm309KIsB8iHEza yEDg== 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=fDcvYkIEVq0f5BjuAYxIIri1A/cHLRrOx9YyUXqMPAI=; b=oyDqg2CRM8/r0h819LK75GPrq25spVmdUjH77ycywUq+FNb3wrRHmGJsWOyD0AdT72 U5Bll8XexSUfnWR4O9FZpm51hlakCuWzQMU5xA8oIRvuANmt+38VnK8stPUiajTqsSmS HtFBkZJu1JQkvShriSG45/6uND7OhX/fEpI+dSkQCJYRU9nE+tT7FRK74RQoFyrvjI+a DDvA+/OZLCOeG/TkprFXc3GxQZOIf0iu+8kQ/3o4uTx3ERGcF3YqBfpSoLQfltCS/1w4 9ILkFkDxObKacRC0mXIvRDpPsZ4bDno9mAjsbHd29TOFG/eU4BrSucCGHCTbIV8pSs7h aufA== X-Gm-Message-State: AOAM5322ieGS6Qxi++bIzX559SHcqSYHYIb9w1iMqKHP4grkL3LQ1DT4 z9KWeRK9+aGRNJF0gEskiiUkJw== X-Google-Smtp-Source: ABdhPJw6YN/NpLXgV8emVgfWbE/XMoacETKHzCEKKobJ+5XMQwN9fvrsU3zZ93bJ71gUMnzQUAZ8xg== X-Received: by 2002:a50:8d09:0:b0:41c:b898:19a6 with SMTP id s9-20020a508d09000000b0041cb89819a6mr24551282eds.30.1649510690712; Sat, 09 Apr 2022 06:24:50 -0700 (PDT) Received: from [192.168.0.188] (xdsl-188-155-201-27.adslplus.ch. [188.155.201.27]) by smtp.gmail.com with ESMTPSA id m20-20020a170906235400b006e718d8b849sm7846661eja.45.2022.04.09.06.24.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 09 Apr 2022 06:24:50 -0700 (PDT) Message-ID: Date: Sat, 9 Apr 2022 15:24:49 +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 05/18] MIPS: DTS: jz4780: fix pinctrl as reported by dtbscheck Content-Language: en-US To: "H. Nikolaus Schaller" Cc: Rob Herring , Paul Cercueil , Thomas Bogendoerfer , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-mips@vger.kernel.org, letux-kernel@openphoenux.org References: <1941bc4ed553b27f399ad00ea61ff2b0237d14e3.1649443080.git.hns@goldelico.com> <530E0F7F-FC03-45DD-BF87-D049D3108AD3@goldelico.com> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 09/04/2022 15:22, H. Nikolaus Schaller wrote: >> >> What does that mean? One cannot create multiple patches and apply them? > > This patch set was created by some automatic scripts. And they produce one patch > per group of warnings. > > But here you ask me to merge 4 unrelated topics into a single one. > > Or do you mean something else? You can edit a commit, right? git commit --amend? So where is the problem? > >> >>> And they are not related. Every one is based on a different .yaml >>> schema file. >> >> Which does not matter, because the name of the node does not matter. We >> enforce it in schema to makes things organized and easier in testing. >> This does not fix any real problem, just the problem we created by >> ourselves with schema. >> >>> >>> That in all cases the result looks similar comes from similar >>> requirements by the schemata and has no inherent connection. >> >> All schemas will require it, won't they? The same for arm... > > We may be talking about different things here. > > My understanding: > you ask me to merge 5/18, 8/18, 9/18, 12/18 because they contain "controller" in the node-name. > > Right? If not then we must clarify that first. No. I ask you to fix all pin-controller cases, for entire MIPS, not just one. And in one month one more. And then again one more. Best regards, Krzysztof