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 181F9C433FE for ; Fri, 20 May 2022 11:54:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1348802AbiETLyN (ORCPT ); Fri, 20 May 2022 07:54:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37444 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1348792AbiETLyM (ORCPT ); Fri, 20 May 2022 07:54:12 -0400 Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3AB8D15E499 for ; Fri, 20 May 2022 04:54:10 -0700 (PDT) Received: by mail-lf1-x130.google.com with SMTP id f4so13851730lfu.12 for ; Fri, 20 May 2022 04:54:10 -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=rSuzs4n4Sskm3JHT6PT66YWFV3PUZnimPTSzRD2tWSg=; b=wpU0Xbi3qNPhIsGbn3dTnIJjM0guksk6R0+2fenSiGhdpViMAQwecBOTD6TSGuyT+E uUB+KkSPJLE2hZE1m+XHi+XvIEOYhdcwkMwKILksmRBLUSEF0AChl22J2FR+pR8Y6aoM I6/nj+/ttx8o2pLGwFJmgVnxj/97Rp3IPxhNEoUV5nPKZTBvpzDr3ZGvseVYJROTwCte u4DUBrDePqhdXtUs4xQWmHYCUHf4tfeMllUs7Pr7MU2nW8LpOHLwL5+MIHHyNC+B3n4G 6f5gY/5q/MMUUfU/9/CRzhAghdlEx6ErskRuy18t0iwPlUpIVTM9kMf4eZgqm4ztSp7A DdMQ== 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=rSuzs4n4Sskm3JHT6PT66YWFV3PUZnimPTSzRD2tWSg=; b=KXyHVn8SMtNBkvcOG2nqeTWFqaCXoTtO117UzxnamLyTYKf6wAvabkEpNBXVLXEXfF POaxBA2XuQO8454Ixj0g5rY/T6dOhLzTPnVp1w/6xZUFdK1ViXk2xTxBVDBJEr863VX3 qjYrAuC2twZ/GYnGRx7EGNRFKFbcxnNrPY+Ti1mzbc/Q0R+dRmg/pWHea0kUK9GZUPkA 9UFPXq8BmAwn9XhPK0+irfkE2AV9KTyp9bL48U/J/A0x4J1kbnplhMSw6GskR1hx2Las 6IsNik7rr+vH/IsaAeftiJ6z92N0rsjZSjx+AMZRzQT3rjJk2o4EWiXbGsonIIgWYRrA 2XRg== X-Gm-Message-State: AOAM5330OS1fcV4zxVMbLR0y7xc48xB+LKMlZq4Sayjz3RaUiPGqxS5g N1OVdHY1EkMqK4NFWLLpDmKowA== X-Google-Smtp-Source: ABdhPJwHbS3B+g10NGZBGRxnNDfdHe7p/uRXjL55A1oYzFJvqnTHUNryLFfceBT55K+P1aalTA9hvg== X-Received: by 2002:ac2:43a1:0:b0:478:5867:5047 with SMTP id t1-20020ac243a1000000b0047858675047mr1004918lfl.37.1653047648614; Fri, 20 May 2022 04:54:08 -0700 (PDT) Received: from [192.168.0.17] (78-11-189-27.static.ip.netia.com.pl. [78.11.189.27]) by smtp.gmail.com with ESMTPSA id o12-20020ac2494c000000b0047255d211a5sm632074lfi.212.2022.05.20.04.54.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 20 May 2022 04:54:08 -0700 (PDT) Message-ID: Date: Fri, 20 May 2022 13:54:06 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 Subject: Re: [PATCH 2/2] dt-bindings: arm: qcom: Document xiaomi,natrium board Content-Language: en-US To: Alec Su , Rob Herring Cc: linux-kernel@vger.kernel.org, robh+dt@kernel.org, bjorn.andersson@linaro.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, y.oudjana@protonmail.com, krzysztof.kozlowski+dt@linaro.org, agross@kernel.org, sboyd@codeaurora.org References: <20220519074112.25600-1-ae40515@yahoo.com.tw> <20220519074112.25600-3-ae40515@yahoo.com.tw> <1652965539.974526.1359566.nullmailer@robh.at.kernel.org> <7e5ecca1-aef7-ce90-7797-7f8be3b55715@yahoo.com.tw> From: Krzysztof Kozlowski In-Reply-To: <7e5ecca1-aef7-ce90-7797-7f8be3b55715@yahoo.com.tw> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On 20/05/2022 03:23, Alec Su wrote: > On 2022/5/19 21:05, Rob Herring wrote: >> On Thu, 19 May 2022 07:41:12 +0000, Alec Su wrote: >>> Document Xiaomi Mi 5s Plus (xiaomi-natrium) smartphone which is based on >>> Snapdragon 821 SoC. > > I checked the full log. These warnings seem not the new warning caused > by the patch series. Look like these device trees are trying to match > with each of the compatible strings in qcom.yaml. Yes, I'll fix them. Best regards, Krzysztof