From: Rob Herring <robh@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Frank Rowand <frowand.list@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: [GIT PULL] Devicetree fixes for v5.17, take 3
Date: Tue, 8 Mar 2022 13:43:06 -0600 [thread overview]
Message-ID: <YiexypCIC3q8dHPZ@robh.at.kernel.org> (raw)
Linus,
Please pull 2 more fixes for v5.17.
Rob
The following changes since commit 0c0822bcb73f154d96ee648644ec5a8628e3b864:
dt-bindings: update Roger Quadros email (2022-02-22 16:06:31 -0600)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git tags/devicetree-fixes-for-5.17-3
for you to fetch changes up to f6eafa4022dd61e029205bea4d4147d26e69fef2:
dt-bindings: phy: ti,tcan104x-can: Document mux-states property (2022-03-08 10:41:32 -0600)
----------------------------------------------------------------
Devicetree fixes for v5.17, take 3:
- Fix pinctrl node name warnings in examples
- Add missing 'mux-states' property in ti,tcan104x-can binding
----------------------------------------------------------------
Aswath Govindraju (1):
dt-bindings: phy: ti,tcan104x-can: Document mux-states property
Rob Herring (1):
dt-bindings: mfd: Fix pinctrl node name warnings
Documentation/devicetree/bindings/mfd/brcm,cru.yaml | 4 ++--
Documentation/devicetree/bindings/mfd/cirrus,lochnagar.yaml | 6 +++---
Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml | 7 +++++++
Documentation/devicetree/bindings/pinctrl/cirrus,madera.yaml | 3 ---
4 files changed, 12 insertions(+), 8 deletions(-)
next reply other threads:[~2022-03-08 19:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 19:43 Rob Herring [this message]
2022-03-08 20:16 ` [GIT PULL] Devicetree fixes for v5.17, take 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=YiexypCIC3q8dHPZ@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=krzysztof.kozlowski@canonical.com \
--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