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 AE878C433FE for ; Mon, 7 Nov 2022 18:40:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232315AbiKGSki (ORCPT ); Mon, 7 Nov 2022 13:40:38 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50076 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232582AbiKGSkE (ORCPT ); Mon, 7 Nov 2022 13:40:04 -0500 Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 66DA31A062 for ; Mon, 7 Nov 2022 10:40:02 -0800 (PST) Received: by mail-lj1-x231.google.com with SMTP id x21so17639542ljg.10 for ; Mon, 07 Nov 2022 10:40:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=zu8Huj0bPMNsIqjTrIRXl4tf9CZ1yQ2L0lxIAXL9iVs=; b=gBzEObADVp5mtqxgk+lzuUPqMxxAL9wosa04e075/qjVZ6gNiviehxXI/wwbI+DxHR BNPEqlSI+gtimj4nm2oFGHs1nboOysYSyuV4oaMazFVnwBv9XnghnFfK/ixI9XsKUAUW Goz9k+U86atux9bLF8z+y1AOfXbAIoPzNbh+gSEfNLredoBbJyqZwQcE4OiIZRtAnv/a rTI2p9KyriA6/E5DG/niYmrgeI5Qb5ZOBeRK6KS59pxJBdTVjxRDZyvolbf077VpICjt kxhvzP3kOs5BY/nmjrJ8LRpeW6uEPM/B+9MpIMiNr8qFANxTmRb38Vvwadd9sVq8Mi7s wvZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=zu8Huj0bPMNsIqjTrIRXl4tf9CZ1yQ2L0lxIAXL9iVs=; b=fZF9evmG/YrO4CIhGx8jRKeGQ7jzk0Gdv4nnRIy0NfQ6FpKEhWTgYJg/PXnd1l+P57 yO5RmmadZD9OdyQcdU/Dk4EcIumv6JKPU89SEo01nIy/fL+we06lETP+tL9N/xZ/5sH0 tyS1RPfO2V1YOF5uHARY0g3rK5Oll6W5xDAaS31KuwEgSBx1RieiOYFt9TOKj7Te6T7g NqDk8IFj0Wal36gVqhP+fx5C9DrAkzTcl6xY6Ss6izMIgSGUoRZcEnTUV6kBtH7ETan1 gwm43o2/U2Yv+E/EGtK76rOZmrO67Rv3dzQ1prycqXbmzpzerc/NA/WpeS5S9dm4ZIvs eVpw== X-Gm-Message-State: ACrzQf2TbgRrDL2qAXbAVcNFPFW4dN2LhP9serZOfCjiR079hCGE+BoC h6xNlnMy4xMm9HTQvKrFQz9raA== X-Google-Smtp-Source: AMsMyM4QyMCFiYp6kD2IUfKXFyDf1b18akD1Z4DGlZsS3MTzqmC+0aBlDgaBeRfmZITKdcqgY0tZvA== X-Received: by 2002:a05:651c:c6:b0:277:c75:e295 with SMTP id 6-20020a05651c00c600b002770c75e295mr5586206ljr.228.1667846400799; Mon, 07 Nov 2022 10:40:00 -0800 (PST) Received: from [192.168.0.20] (088156142199.dynamic-2-waw-k-3-2-0.vectranet.pl. [88.156.142.199]) by smtp.gmail.com with ESMTPSA id p25-20020a2eb119000000b002770fb5722fsm1376743ljl.123.2022.11.07.10.39.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 07 Nov 2022 10:40:00 -0800 (PST) Message-ID: Date: Mon, 7 Nov 2022 19:39:59 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: [PATCH v2 1/2] dt-bindings: i2c: renesas,rzv2m: Fix SoC specific string Content-Language: en-US To: Fabrizio Castro , Rob Herring , Krzysztof Kozlowski , Geert Uytterhoeven Cc: Magnus Damm , Biju Das , Wolfram Sang , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org, Chris Paterson , Biju Das , Laurent Pinchart , Jacopo Mondi References: <20221107165027.54150-1-fabrizio.castro.jz@renesas.com> <20221107165027.54150-2-fabrizio.castro.jz@renesas.com> From: Krzysztof Kozlowski In-Reply-To: <20221107165027.54150-2-fabrizio.castro.jz@renesas.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 07/11/2022 17:50, Fabrizio Castro wrote: > The preferred form for Renesas' compatible strings is: > ",-" > > Somehow the compatible string for the r9a09g011 I2C IP was upstreamed > as renesas,i2c-r9a09g011 instead of renesas,r9a09g011-i2c, which > is really confusing, especially considering the generic fallback > is renesas,rzv2m-i2c. > > The first user of renesas,i2c-r9a09g011 in the kernel is not yet in > a kernel release, it will be in v6.1, therefore it can still be > fixed in v6.1. > Even if we don't fix it before v6.2, I don't think there is any > harm in making such a change. > > s/renesas,i2c-r9a09g011/renesas,r9a09g011-i2c/g for consistency. > > Fixes: ba7a4d15e2c4 ("dt-bindings: i2c: Document RZ/V2M I2C controller") > Signed-off-by: Fabrizio Castro Reviewed-by: Krzysztof Kozlowski Best regards, Krzysztof