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 646DAC43334 for ; Mon, 6 Jun 2022 07:34:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231160AbiFFHem (ORCPT ); Mon, 6 Jun 2022 03:34:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37026 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231195AbiFFHej (ORCPT ); Mon, 6 Jun 2022 03:34:39 -0400 Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AD70122518 for ; Mon, 6 Jun 2022 00:34:37 -0700 (PDT) Received: by mail-ed1-x536.google.com with SMTP id v19so17600512edd.4 for ; Mon, 06 Jun 2022 00:34:37 -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=f+ScugHy4AlcscEnldL2i5PmbfvQGH4t+6gM1Or5hQU=; b=vClp7zDdiSSua3oBwwpibNjZV1/FgtOu6YjrqDwUTJeboiE7xMBaRmFzZMij4Ifk4V wi1bRx7Z9cZm8iePc4KGYsAxqQaczdTNO0TuWLC8sfYe58H85wFqY/tTJYRNnFpoENnd q/Q6OcXje+KY0K+IBjZYvdv9ubDHESPmjIzGv/ZQHo5WiZzovNe1QccTp6zliv/2bjRy 8bO8xx8Rx5LzCmfv8xmrsU9sHqkxzHw14kni133wgXHF+3wjZDjumWn+4mZkQyH+ygl9 Od415jviG4Ua4gqf4lZaqwnvChKc2TkvTQaRd05vx77YDjoRUphETVbVnVhB5QUpH/9Q mVAQ== 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=f+ScugHy4AlcscEnldL2i5PmbfvQGH4t+6gM1Or5hQU=; b=Ue0kqZOQLCKPyABynwTDQ/I2VfKx/VwXaSyVU2hoyVN8//reS5DEWuiaNVQf9SdJPy uqDH5TupDrVfJyknI0okm/sgOgq7RFUbJquFPfGCHGP9uiMdIvL19okd+vxmDq3jflOP 11e72sfp2NgOOhn1HnXmVMYk7jpWM1h74M6JUEmpuH8wuXETfJ043asWSr6lIlVDF28v gvxCO2wRBhO0rGoUn6b0ZSshxh3eaqvaP6CBji3A8uiXY9UJ1XFJO61j4jZeEJIZZMxy c2FM8p+DNfBFXe7TxzCIz0rrTlxtOAQDzuutGY9VzCCWYr6tEUU8+M875y+TqCo9I55n 7/Yg== X-Gm-Message-State: AOAM532RTu5AKu73jgZ7Iibj1VjzOsHPdG06cXnP8a2cMUUnvdEDRNmM T18GYwEF9CpJJgR/s0hh4GHHyA== X-Google-Smtp-Source: ABdhPJzsdrYxbqs5FgA4BhHAFfwRp0nwo5WvSOzpYDmPzZFoFqOex6Gm7p+2PUm7Ju5jyIpMQcx65g== X-Received: by 2002:a05:6402:1cb5:b0:42d:ddda:7459 with SMTP id cz21-20020a0564021cb500b0042dddda7459mr25843817edb.16.1654500876277; Mon, 06 Jun 2022 00:34:36 -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 f7-20020a170906560700b006fef5088792sm5980417ejq.108.2022.06.06.00.34.35 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 06 Jun 2022 00:34:35 -0700 (PDT) Message-ID: Date: Mon, 6 Jun 2022 09:34:34 +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 v1 0/6] clear riscv dtbs_check errors Content-Language: en-US To: mail@conchuod.ie, Rob Herring , Krzysztof Kozlowski , Andrew Lunn , Support Opensource , Lee Jones , Ulf Hansson , Palmer Dabbelt , Paul Walmsley , Albert Ou , Steve Twiss Cc: Conor Dooley , linux-i2c@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org, linux-riscv@lists.infradead.org, Atul Khare References: <20220605133300.376161-1-mail@conchuod.ie> From: Krzysztof Kozlowski In-Reply-To: <20220605133300.376161-1-mail@conchuod.ie> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-i2c@vger.kernel.org On 05/06/2022 15:32, mail@conchuod.ie wrote: > From: Conor Dooley > > Hey, > Couple conversions from txt to yaml here with the intent of fixing the > the dtbs_check warnings for riscv. Atul Khare already sent patches for > the gpio-line-names & cache-sets (which went awol) and will clear the > remaining two errors. > > Rob/Krzysztof: > Have I correctly expressed the mutually exclusive properties? > I had a look around, but wasn't able to find an obvious binding to ape. I'll take a look. > > Wasn't sure if a txt -> yaml conversion's MAINTAINERS update was meant > to be in the same patch or not, so feel free to squash. It's the same patch, so please squash with next release. Best regards, Krzysztof