All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: arm-soc <arm@kernel.org>, soc@kernel.org
Cc: Hans Ulli Kroll <ulli.kroll@googlemail.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] Gemini updates for v5.4 take one
Date: Sat, 3 Aug 2019 15:53:27 +0200	[thread overview]
Message-ID: <CACRpkdarsQNfXgXMQKfYwOyiqhKY67gKd3ufQ+wexwO3v=LE5w@mail.gmail.com> (raw)

Hi ARM SoC folks,

here are some Gemini patches for the v5.4 kernel cycle,
maybe there will be more, who knows.

Details in the signed tag, please pull it in!

Yours,
Linus Walleij

The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:

  Linus 5.3-rc1 (2019-07-21 14:05:38 -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.4-1

for you to fetch changes up to e8547e12d5d6a40a16263cc8678d7025e54c379a:

  ARM: dts: gemini: Mount root from mtdblock3 (2019-07-26 13:42:57 +0200)

----------------------------------------------------------------
DTS updates for the Gemini platform:

- Fix up some pin config confusion

- Use redboot partition parsing on the SL93512r

- Mount root on mtdblock3 by default

----------------------------------------------------------------
Linus Walleij (3):
      ARM: dts: gemini: Fix up confused pin settings
      ARM: dts: gemini: Switch to redboot partition parsing
      ARM: dts: gemini: Mount root from mtdblock3

 arch/arm/boot/dts/gemini-nas4220b.dts | 37 ++++-------------------
 arch/arm/boot/dts/gemini-sl93512r.dts | 56 ++++++++++-------------------------
 2 files changed, 21 insertions(+), 72 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-08-03 13:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CACRpkdarsQNfXgXMQKfYwOyiqhKY67gKd3ufQ+wexwO3v=LE5w@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=soc@kernel.org \
    --cc=ulli.kroll@googlemail.com \
    /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.