From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
Stanislav Jakubek <stano.jakubek@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Cc: linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ARM: dts: bcm23550: Add SoC-specific I2C compatible
Date: Mon, 8 May 2023 11:54:06 -0700 [thread overview]
Message-ID: <20230508185406.1639539-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <9875ec0211187e4f5e2a4379c63eacdb69b31d7a.1682252615.git.stano.jakubek@gmail.com>
On Sun, 23 Apr 2023 14:39:12 +0200, Stanislav Jakubek <stano.jakubek@gmail.com> wrote:
> Add BCM23550-specific compatible for brcm,kona-i2c nodes. While not
> currently used by the i2c-bcm-kona driver, they can serve for further
> customization, if required.
> Done in preparation for dt-binding coversion to DT schema.
>
> Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.com>
> ---
Applied to https://github.com/Broadcom/stblinux/commits/devicetree/next, thanks!
--
Florian
prev parent reply other threads:[~2023-05-08 18:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 12:39 [PATCH v2 1/2] ARM: dts: bcm23550: Add SoC-specific I2C compatible Stanislav Jakubek
2023-04-23 12:40 ` [PATCH v2 2/2] dt-bindings: i2c: brcm,kona-i2c: convert to YAML Stanislav Jakubek
2023-04-24 13:28 ` Rob Herring
2023-04-26 17:23 ` Stanislav Jakubek
2023-04-30 6:55 ` Wolfram Sang
2023-04-30 12:12 ` Krzysztof Kozlowski
2023-05-03 15:38 ` Wolfram Sang
2023-04-24 13:53 ` Krzysztof Kozlowski
2023-04-26 17:16 ` Stanislav Jakubek
2023-04-27 15:54 ` Krzysztof Kozlowski
2023-05-04 4:22 ` Wolfram Sang
2023-05-08 18:54 ` Florian Fainelli [this message]
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=20230508185406.1639539-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=stano.jakubek@gmail.com \
/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).