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 v5.9, take 2
Date: Fri, 21 Aug 2020 21:25:40 -0600	[thread overview]
Message-ID: <20200822032540.GA2215775@bogus> (raw)

Linus,

Please pull another set of DT fixes.

Rob


The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:

  Linux 5.9-rc1 (2020-08-16 13:04:57 -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.9-2

for you to fetch changes up to 5cd841d2676a702e5f79a8bacbfbae3bfc2411f7:

  dt-bindings: vendor-prefixes: Remove trailing whitespace (2020-08-21 16:27:57 -0600)

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

- Restore range parsing error check

- Workaround PCI range parsing with missing 'device_type' now required

- Correct description of 'phy-connection-type'

- Fix erroneous matching on 'snps,dw-pcie' by 'intel,lgm-pcie' schema

- A couple of grammar and whitespace fixes

- Update Shawn Guo's email

----------------------------------------------------------------
Colin Ian King (1):
      of/address: check for invalid range.cpu_addr

Fabio Estevam (1):
      dt-bindings: Use Shawn Guo's preferred e-mail for i.MX bindings

Geert Uytterhoeven (2):
      dt: writing-schema: Miscellaneous grammar fixes
      dt-bindings: vendor-prefixes: Remove trailing whitespace

Madalin Bucur (1):
      dt-bindings: net: correct description of phy-connection-type

Marc Zyngier (1):
      of: address: Work around missing device_type property in pcie nodes

Rob Herring (1):
      dt-bindings: PCI: intel,lgm-pcie: Fix matching on all snps,dw-pcie instances

 .../devicetree/bindings/clock/imx23-clock.yaml      |  2 +-
 .../devicetree/bindings/clock/imx28-clock.yaml      |  2 +-
 .../devicetree/bindings/gpio/gpio-mxs.yaml          |  2 +-
 Documentation/devicetree/bindings/i2c/i2c-mxs.yaml  |  2 +-
 .../devicetree/bindings/mmc/fsl-imx-esdhc.yaml      |  2 +-
 Documentation/devicetree/bindings/mmc/mxs-mmc.yaml  |  2 +-
 .../bindings/net/ethernet-controller.yaml           |  3 ++-
 .../devicetree/bindings/pci/intel-gw-pcie.yaml      |  8 ++++++++
 Documentation/devicetree/bindings/pwm/mxs-pwm.yaml  |  2 +-
 .../devicetree/bindings/spi/fsl-imx-cspi.yaml       |  2 +-
 .../devicetree/bindings/thermal/imx-thermal.yaml    |  2 +-
 .../devicetree/bindings/vendor-prefixes.yaml        |  2 +-
 Documentation/devicetree/writing-schema.rst         |  4 ++--
 drivers/of/address.c                                | 21 ++++++++++++++++++++-
 14 files changed, 42 insertions(+), 14 deletions(-)

             reply	other threads:[~2020-08-22  3:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-22  3:25 Rob Herring [this message]
2020-08-22 17:32 ` [GIT PULL] Devicetree fixes for v5.9, take 2 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=20200822032540.GA2215775@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