All of lore.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.4
Date: Fri, 4 Oct 2019 08:22:03 -0500	[thread overview]
Message-ID: <20191004132203.GA29838@bogus> (raw)

Hi Linus,

Please pull a few DT fixes for 5.4.

Rob

The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:

  Linux 5.4-rc1 (2019-09-30 10:35:40 -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.4

for you to fetch changes up to f437ade3296bacaddb6d7882ba0515940f01daf4:

  dt-bindings: phy: lantiq: Fix Property Name (2019-10-02 14:14:58 -0500)

----------------------------------------------------------------
DeviceTree fixes for v5.4:

Fix several 'dt_binding_check' build failures.

----------------------------------------------------------------
Maxime Ripard (5):
      dt-bindings: dsp: Fix fsl,dsp example
      dt-bindings: media: rc: Fix redundant string
      dt-bindings: iio: ad7192: Fix Regulator Properties
      dt-bindings: iio: ad7192: Fix DTC warning in the example
      dt-bindings: phy: lantiq: Fix Property Name

 Documentation/devicetree/bindings/dsp/fsl,dsp.yaml                | 1 +
 Documentation/devicetree/bindings/iio/adc/adi,ad7192.yaml         | 7 +++----
 Documentation/devicetree/bindings/media/rc.yaml                   | 1 -
 Documentation/devicetree/bindings/phy/lantiq,vrx200-pcie-phy.yaml | 2 +-
 4 files changed, 5 insertions(+), 6 deletions(-)

             reply	other threads:[~2019-10-04 13:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04 13:22 Rob Herring [this message]
2019-10-04 20:40 ` [GIT PULL] Devicetree fixes for v5.4 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=20191004132203.GA29838@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.