From: Rob Herring <robh@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Frank Rowand <frowand.list@gmail.com>
Subject: [GIT PULL] Devicetree fixes for v5.6
Date: Wed, 5 Feb 2020 09:25:06 +0000 [thread overview]
Message-ID: <20200205092506.GA31689@bogus> (raw)
Linus,
Please pull a couple of DT fixes for rc1.
Rob
The following changes since commit 33b40134e5cfbbccad7f3040d1919889537a3df7:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (2020-02-04 13:32:20 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git tags/devicetree-fixes-for-5.6
for you to fetch changes up to 04dbd86539fd2f0a65fdd5a0416b7f6606f95e16:
dt-bindings: Fix paths in schema $id fields (2020-02-05 09:14:57 +0000)
----------------------------------------------------------------
Devicetree fixes for v5.6:
- Fix incorrect $id paths in schemas
- 2 fixes for Intel LGM SoC binding schemas
----------------------------------------------------------------
Dilip Kota (1):
dt-bindings: PCI: intel: Fix dt_binding_check compilation failure
Rob Herring (2):
dt-bindings: phy: Fix errors in intel,lgm-emmc-phy example
dt-bindings: Fix paths in schema $id fields
Documentation/devicetree/bindings/arm/fsl.yaml | 2 +-
Documentation/devicetree/bindings/arm/qcom.yaml | 2 +-
Documentation/devicetree/bindings/clock/bitmain,bm1880-clk.yaml | 2 +-
Documentation/devicetree/bindings/clock/fsl,sai-clock.yaml | 2 +-
Documentation/devicetree/bindings/clock/imx8mn-clock.yaml | 2 +-
Documentation/devicetree/bindings/clock/imx8mp-clock.yaml | 2 +-
Documentation/devicetree/bindings/clock/milbeaut-clock.yaml | 2 +-
Documentation/devicetree/bindings/clock/qcom,dispcc.yaml | 2 +-
Documentation/devicetree/bindings/clock/qcom,gcc.yaml | 2 +-
Documentation/devicetree/bindings/clock/qcom,gpucc.yaml | 2 +-
Documentation/devicetree/bindings/clock/qcom,mmcc.yaml | 2 +-
Documentation/devicetree/bindings/clock/qcom,rpmhcc.yaml | 2 +-
Documentation/devicetree/bindings/clock/qcom,videocc.yaml | 2 +-
Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml | 2 +-
Documentation/devicetree/bindings/clock/xlnx,versal-clk.yaml | 2 +-
Documentation/devicetree/bindings/hwmon/adi,ltc2947.yaml | 2 +-
Documentation/devicetree/bindings/iio/adc/adi,ad7124.yaml | 2 +-
Documentation/devicetree/bindings/iio/adc/adi,ad7192.yaml | 2 +-
Documentation/devicetree/bindings/iio/adc/microchip,mcp3911.yaml | 2 +-
Documentation/devicetree/bindings/iio/adc/st,stm32-dfsdm-adc.yaml | 2 +-
Documentation/devicetree/bindings/iio/dac/lltc,ltc1660.yaml | 2 +-
Documentation/devicetree/bindings/input/gpio-vibrator.yaml | 2 +-
Documentation/devicetree/bindings/pci/intel-gw-pcie.yaml | 4 +---
Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml | 4 +++-
24 files changed, 26 insertions(+), 26 deletions(-)
next reply other threads:[~2020-02-05 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 9:25 Rob Herring [this message]
2020-02-05 18:20 ` [GIT PULL] Devicetree fixes for v5.6 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=20200205092506.GA31689@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.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;
as well as URLs for NNTP newsgroup(s).