From: Wolfram Sang <wsa@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Stanislav Jakubek <stano.jakubek@gmail.com>,
Rob Herring <robh@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Ray Jui <rjui@broadcom.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] dt-bindings: i2c: brcm,kona-i2c: convert to YAML
Date: Wed, 3 May 2023 17:38:19 +0200 [thread overview]
Message-ID: <ZFJ/67UgNRmB44HT@sai> (raw)
In-Reply-To: <d10e48cf-3cf8-89b7-8741-260adccfdfed@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 219 bytes --]
> The dtbs warnings - if fixed via any other pactch - can be safely
> ignored. They do not affect bisectability. Please grab this patch via
> I2C. The DTS will go separately via arm-soc.
OK, thanks for the heads up!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-05-03 15:38 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 [this message]
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 ` [PATCH v2 1/2] ARM: dts: bcm23550: Add SoC-specific I2C compatible Florian Fainelli
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=ZFJ/67UgNRmB44HT@sai \
--to=wsa@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@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=robh@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).