devicetree.vger.kernel.org archive mirror
 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>,
	Guenter Roeck <linux@roeck-us.net>
Subject: [GIT PULL] Devicetree fixes for v5.12-rc, take 2
Date: Fri, 9 Apr 2021 15:00:09 -0500	[thread overview]
Message-ID: <20210409200009.GA4050302@robh.at.kernel.org> (raw)

Linus,

Please pull. This has the fix for the OpenRisc regression Guenter 
reported.

Rob


The following changes since commit b5a95bb1883e2bac1009cc88e65c71cff6f931e6:

  dt-bindings: media: Use graph and video-interfaces schemas, round 2 (2021-03-01 11:30:21 -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.12-2

for you to fetch changes up to d473d32c2fbac2d1d7082c61899cfebd34eb267a:

  of: property: fw_devlink: do not link ".*,nr-gpios" (2021-04-09 14:24:25 -0500)

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

- Fix fw_devlink failure with ".*,nr-gpios" properties

- Doc link reference fixes from Mauro

- Fixes for unaligned FDT handling found on OpenRisc. First, avoid
  crash with better error handling when unflattening an unaligned FDT.
  Second, fix memory allocations for FDTs to ensure alignment.

----------------------------------------------------------------
Frank Rowand (2):
      of: properly check for error returned by fdt_get_name()
      of: unittest: overlay: ensure proper alignment of copied FDT

Ilya Lipnitskiy (1):
      of: property: fw_devlink: do not link ".*,nr-gpios"

Mauro Carvalho Chehab (3):
      dt-bindings: don't use ../dir for doc references
      dt-bindings: fix references for iio-bindings.txt
      dt-bindings:iio:adc: update motorola,cpcap-adc.yaml reference

 .../devicetree/bindings/hwmon/ntc_thermistor.txt   |  2 +-
 .../devicetree/bindings/iio/adc/ingenic,adc.yaml   |  5 +--
 .../devicetree/bindings/input/adc-joystick.yaml    |  4 ++-
 .../input/touchscreen/resistive-adc-touch.txt      |  5 ++-
 Documentation/devicetree/bindings/mfd/ab8500.txt   |  4 ++-
 .../devicetree/bindings/mfd/motorola-cpcap.txt     | 16 +++++-----
 drivers/of/fdt.c                                   | 36 ++++++++++++++--------
 drivers/of/of_private.h                            |  2 ++
 drivers/of/overlay.c                               | 24 +++++++++------
 drivers/of/property.c                              | 11 ++++++-
 drivers/of/unittest.c                              | 22 +++++++++----
 11 files changed, 88 insertions(+), 43 deletions(-)

             reply	other threads:[~2021-04-09 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 20:00 Rob Herring [this message]
2021-04-09 20:09 ` [GIT PULL] Devicetree fixes for v5.12-rc, 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=20210409200009.GA4050302@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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).