From: Fabrizio Castro <fabrizio.castro.jz@renesas.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
Wolfram Sang <wsa@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Jacopo Mondi <jacopo@jmondi.org>
Subject: [PATCH v2 0/2] Fix r9a09g011 specific I2C compatible string
Date: Mon, 7 Nov 2022 16:50:25 +0000 [thread overview]
Message-ID: <20221107165027.54150-1-fabrizio.castro.jz@renesas.com> (raw)
Dear All,
The preferred form for Renesas' compatible strings is:
"<vendor>,<family>-<module>"
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.
Since it's early days for r9a09g011.dtsi, and compatible
renesas,i2c-r9a09g011 isn't being actively used at the moment,
I think it's safe to change to make compatible strings less
confusing.
v2 - Improved changelogs
Thanks,
Fab
Fabrizio Castro (2):
dt-bindings: i2c: renesas,rzv2m: Fix SoC specific string
arm64: dts: renesas: r9a09g011: Fix I2C SoC specific strings
Documentation/devicetree/bindings/i2c/renesas,rzv2m.yaml | 4 ++--
arch/arm64/boot/dts/renesas/r9a09g011.dtsi | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
--
2.34.1
next reply other threads:[~2022-11-07 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 16:50 Fabrizio Castro [this message]
2022-11-07 16:50 ` [PATCH v2 1/2] dt-bindings: i2c: renesas,rzv2m: Fix SoC specific string Fabrizio Castro
2022-11-07 18:39 ` Krzysztof Kozlowski
2023-01-16 16:16 ` Fabrizio Castro
2023-01-16 21:41 ` Wolfram Sang
2023-01-17 17:48 ` Fabrizio Castro
2022-11-07 16:50 ` [PATCH v2 2/2] arm64: dts: renesas: r9a09g011: Fix I2C SoC specific strings Fabrizio Castro
2022-11-08 9:06 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221107165027.54150-1-fabrizio.castro.jz@renesas.com \
--to=fabrizio.castro.jz@renesas.com \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jacopo@jmondi.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh+dt@kernel.org \
--cc=wsa@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).