From: Wolfram Sang <wsa@kernel.org>
To: "Rafał Miłecki" <rafal@milecki.pl>
Cc: "Rob Herring" <robh@kernel.org>,
"Rafał Miłecki" <zajec5@gmail.com>,
devicetree@vger.kernel.org, "Ray Jui" <rjui@broadcom.com>,
"Rob Herring" <robh+dt@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
"Florian Fainelli" <f.fainelli@gmail.com>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Scott Branden" <sbranden@broadcom.com>
Subject: Re: [PATCH] dt-bindings: i2c: brcm,iproc-i2c: convert to the json-schema
Date: Fri, 28 May 2021 11:57:43 +0200 [thread overview]
Message-ID: <YLC+l1kvyyjrYRdK@kunai> (raw)
In-Reply-To: <80afe993-68f2-01f1-a13e-319a6ec32169@milecki.pl>
[-- Attachment #1.1: Type: text/plain, Size: 446 bytes --]
> I've already got wm8750 YAML binding queued for the 5.14, see linux-next:
> ASoC: wm8750: convert to the json-schema
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=11480dbfe1d59eaa6382864acc476e7621b1da4c
My take is that we can surely accept this binding if there is no build
failure in -next. However, I usually wait for Rob's ack because I don't
know YAML well enough to review patches from other people.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-05-28 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 16:07 [PATCH] dt-bindings: i2c: brcm,iproc-i2c: convert to the json-schema Rafał Miłecki
2021-05-12 18:35 ` [PATCH] dt-bindings: i2c: brcm, iproc-i2c: " Rob Herring
2021-05-28 9:23 ` [PATCH] dt-bindings: i2c: brcm,iproc-i2c: " Wolfram Sang
2021-05-28 9:37 ` Rafał Miłecki
2021-05-28 9:57 ` Wolfram Sang [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=YLC+l1kvyyjrYRdK@kunai \
--to=wsa@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sbranden@broadcom.com \
--cc=zajec5@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).