From: Rob Herring <robh@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Frank Rowand <frowand.list@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: [GIT PULL] Devicetree fixes for v6.4, part 3
Date: Tue, 13 Jun 2023 09:18:14 -0600 [thread overview]
Message-ID: <20230613151814.GA2133279-robh@kernel.org> (raw)
Linus,
Please pull a few DT fixes for 6.4.
Rob
The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git tags/devicetree-fixes-for-6.4-3
for you to fetch changes up to c7753ed71c160f75f92ff5679e9fc22526e56fc5:
dt-bindings: pinctrl: qcom,pmic-mpp: Fix schema for "qcom,paired" (2023-06-13 07:58:47 -0600)
----------------------------------------------------------------
Devicetree fixes for v6.4, part 3:
- Fix missing of_node_put() in init_overlay_changeset()
- Fix schema for qcom,pmic-mpp "qcom,paired" property
- Fix 'additionalProperties' in silvaco,i3c-master binding
- usage-model.rst: Use documented "arm,primecell" compatible string
- Update Damien Le Moal's email address
- Fixes in Realtek Bluetooth binding
----------------------------------------------------------------
Baruch Siach (2):
docs: dt: fix documented Primecell compatible string
docs: zh_CN/devicetree: sync usage-model fix
Chris Morgan (1):
dt-bindings: net: realtek-bluetooth: Fix RTL8821CS binding
Damien Le Moal (1):
dt-bindings: Change Damien Le Moal's contact email
Diederik de Haas (1):
dt-bindings: net: realtek-bluetooth: Fix double RTL8723CS in desc
Krzysztof Kozlowski (1):
dt-bindings: i3c: silvaco,i3c-master: fix missing schema restriction
Kunihiko Hayashi (1):
of: overlay: Fix missing of_node_put() in error case of init_overlay_changeset()
Rob Herring (1):
dt-bindings: pinctrl: qcom,pmic-mpp: Fix schema for "qcom,paired"
Documentation/devicetree/bindings/ata/ahci-common.yaml | 2 +-
Documentation/devicetree/bindings/clock/canaan,k210-clk.yaml | 2 +-
Documentation/devicetree/bindings/i3c/silvaco,i3c-master.yaml | 2 +-
Documentation/devicetree/bindings/mfd/canaan,k210-sysctl.yaml | 2 +-
Documentation/devicetree/bindings/net/realtek-bluetooth.yaml | 4 ++--
Documentation/devicetree/bindings/pinctrl/canaan,k210-fpioa.yaml | 2 +-
Documentation/devicetree/bindings/pinctrl/qcom,pmic-mpp.yaml | 5 +++--
Documentation/devicetree/bindings/reset/canaan,k210-rst.yaml | 2 +-
Documentation/devicetree/bindings/riscv/canaan.yaml | 2 +-
Documentation/devicetree/usage-model.rst | 2 +-
Documentation/translations/zh_CN/devicetree/usage-model.rst | 2 +-
drivers/of/overlay.c | 1 +
12 files changed, 15 insertions(+), 13 deletions(-)
next reply other threads:[~2023-06-13 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 15:18 Rob Herring [this message]
2023-06-13 19:05 ` [GIT PULL] Devicetree fixes for v6.4, part 3 pr-tracker-bot
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=20230613151814.GA2133279-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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