linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: arm-soc <arm@kernel.org>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] Gemini fixes for v5.2
Date: Wed, 19 Jun 2019 13:31:12 +0200	[thread overview]
Message-ID: <CACRpkdbTdVeDaCra3iiaRhf3vby3zMx+WaL+AQ5XhS6VSyGZ7Q@mail.gmail.com> (raw)

Hi ARM SoC folks,

here are two DTS fixes for the Gemini for v5.2. Please
pull them in to ARM SoC.

Yours,
Linus Walleij


The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:

  Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git
tags/gemini-dts-v5.2

for you to fetch changes up to 36558020128b1a48b7bddd5792ee70e3f64b04b0:

  ARM: dts: gemini Fix up DNS-313 compatible string (2019-06-19 13:24:03 +0200)

----------------------------------------------------------------
This fixes up two issues with the Gemini DTS files:
- Blank console after a while on the DIR-685 so as
  not to waste power
- Fix up the erroneous compatible string on the DNS-313

----------------------------------------------------------------
Linus Walleij (2):
      ARM: dts: Blank D-Link DIR-685 console
      ARM: dts: gemini Fix up DNS-313 compatible string

 arch/arm/boot/dts/gemini-dlink-dir-685.dts | 2 +-
 arch/arm/boot/dts/gemini-dlink-dns-313.dts | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2019-06-19 11:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19 11:31 Linus Walleij [this message]
2019-06-19 14:26 ` [GIT PULL] Gemini fixes for v5.2 Olof Johansson

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=CACRpkdbTdVeDaCra3iiaRhf3vby3zMx+WaL+AQ5XhS6VSyGZ7Q@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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).