public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 5.8, v2
Date: Thu, 2 Jul 2020 15:39:24 -0600	[thread overview]
Message-ID: <20200702213924.GA1763915@bogus> (raw)

Linus,

Please pull DT fixes for 5.8. I wouldn't normally update dtc at this 
point in the cycle, but I've been waiting on fixes to land upstream for 
a while now.

Rob


The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:

  Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git tags/devicetree-fixes-for-5.8-2

for you to fetch changes up to 0115e6c98c22f3fc7ff7da2a41480483abe95b37:

  dt-bindings: clock: imx: Fix e-mail address (2020-07-01 16:29:11 -0600)

----------------------------------------------------------------
Devicetree fixes for v5.8, take 2:

- Sync dtc to upstream to pick up fixes for I2C bus checks and quiet
  warnings

- Various fixes for DT binding check warnings

- A couple of build fixes/improvements for binding checks

- ReST formatting improvements for writing-schema.rst

- Document reference fixes

----------------------------------------------------------------
Fabio Estevam (5):
      dt-bindings: usb: aspeed: Remove the leading zeroes
      dt-bindings: display: arm: versatile: Pass the sysreg unit name
      dt-bindings: thermal: Remove soc unit address
      dt-bindings: thermal: k3: Fix the reg property
      dt-bindings: clock: imx: Fix e-mail address

Flavio Suligoi (1):
      doc: devicetree: bindings: fix spelling mistake

Kangmin Park (1):
      dt-bindings: mailbox: zynqmp_ipi: fix unit address

Masahiro Yamada (4):
      dt-bindings: bus: uniphier-system-bus: fix warning in example
      dt-bindings: fix error in 'make clean' after 'make dt_binding_check'
      dt-bindings: do not build processed-schema.yaml for 'make dt_binding_check'
      dt-bindings: copy process-schema-examples.yaml to process-schema.yaml

Mauro Carvalho Chehab (5):
      dt: update a reference for reneases pcar file renamed to yaml
      dt: fix broken links due to txt->yaml renames
      dt: Fix broken references to renamed docs
      dt: fix reference to olpc,xo1.75-ec.txt
      docs: dt: minor adjustments at writing-schema.rst

Rob Herring (1):
      scripts/dtc: Update to upstream version v1.6.0-11-g9d7888cbf19c

 Documentation/devicetree/bindings/Makefile         | 38 +++++++++++++++------
 .../devicetree/bindings/arm/freescale/fsl,scu.txt  |  2 +-
 .../bus/socionext,uniphier-system-bus.yaml         |  4 +--
 .../devicetree/bindings/clock/imx27-clock.yaml     |  2 +-
 .../devicetree/bindings/clock/imx31-clock.yaml     |  2 +-
 .../devicetree/bindings/clock/imx5-clock.yaml      |  2 +-
 .../devicetree/bindings/display/bridge/sii902x.txt |  2 +-
 .../bindings/display/imx/fsl-imx-drm.txt           |  4 +--
 .../devicetree/bindings/display/imx/ldb.txt        |  4 +--
 .../display/panel/arm,versatile-tft-panel.yaml     |  2 +-
 .../bindings/display/rockchip/rockchip-drm.yaml    |  2 +-
 .../bindings/gpio/mediatek,mt7621-gpio.txt         |  2 +-
 .../bindings/interrupt-controller/csky,mpintc.txt  |  2 +-
 .../bindings/mailbox/xlnx,zynqmp-ipi-mailbox.txt   |  2 +-
 .../devicetree/bindings/misc/olpc,xo1.75-ec.txt    |  2 +-
 .../devicetree/bindings/net/mediatek-bluetooth.txt |  2 +-
 .../bindings/pinctrl/renesas,pfc-pinctrl.txt       |  2 +-
 .../devicetree/bindings/sound/audio-graph-card.txt |  2 +-
 .../devicetree/bindings/sound/st,sti-asoc-card.txt |  2 +-
 .../devicetree/bindings/spi/qcom,spi-geni-qcom.txt |  2 +-
 .../bindings/thermal/thermal-sensor.yaml           |  2 +-
 .../devicetree/bindings/thermal/thermal-zones.yaml |  2 +-
 .../bindings/thermal/ti,am654-thermal.yaml         |  2 +-
 .../devicetree/bindings/timer/csky,mptimer.txt     |  2 +-
 .../devicetree/bindings/usb/aspeed,usb-vhub.yaml   |  4 +--
 Documentation/devicetree/writing-schema.rst        |  9 +++--
 Documentation/mips/ingenic-tcu.rst                 |  2 +-
 MAINTAINERS                                        |  8 ++---
 scripts/Makefile.lib                               |  7 +++-
 scripts/dtc/checks.c                               | 39 ++++++++++++++++++++--
 scripts/dtc/dtc.h                                  | 31 +++++++++++++++++
 scripts/dtc/flattree.c                             |  2 +-
 scripts/dtc/libfdt/fdt_rw.c                        |  2 +-
 scripts/dtc/libfdt/fdt_sw.c                        |  2 +-
 scripts/dtc/libfdt/libfdt.h                        |  8 +++++
 scripts/dtc/treesource.c                           |  8 ++---
 scripts/dtc/version_gen.h                          |  2 +-
 scripts/dtc/yamltree.c                             |  6 ++--
 38 files changed, 159 insertions(+), 61 deletions(-)

             reply	other threads:[~2020-07-02 21:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 21:39 Rob Herring [this message]
2020-07-03  6:10 ` [GIT PULL] Devicetree fixes for 5.8, v2 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=20200702213924.GA1763915@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