From: khilman@baylibre•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] ARM: Amlogic: DT fix for v4.6-rc
Date: Fri, 08 Apr 2016 16:24:56 -0700 [thread overview]
Message-ID: <7hvb3rlm47.fsf@baylibre.com> (raw)
In-Reply-To: <CAOQ7t2arscn+pe4FpgzEL26rt3HtoMBP2ndSMvGQtqnDuU4pEg@mail.gmail.com> (Carlo Caione's message of "Wed, 30 Mar 2016 21:35:57 +0200")
Carlo Caione <carlo@caione•org> writes:
> This is a fix for v4.6-rc since the Meson8 / Meson8b platforms are
> currently broken.
>
> The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
>
> Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)
>
> are available in the git repository at:
>
> https://github.com/carlocaione/linux-meson tags/meson8-dt-fix
>
> for you to fetch changes up to 11ca873574c2314de9f0cf1adf8b3be88e4e19ae:
>
> documentation: Fix pinctrl documentation for Meson8 / Meson8b
> (2016-03-30 19:51:57 +0200)
>
> ----------------------------------------------------------------
> With http://www.spinics.net/lists/devicetree/msg116771.html we split / refactor
> the pinctrl driver to have two different pinctrl devices for each bus on the
> Amlogic Meson8 / Meson8b SoCs.
> These are the missing patches for documentation and DT that weren't pulled into
> mainline with the driver changes.
>
> ----------------------------------------------------------------
Strictly speaking, these aren't just documentation patches. The missing
.dtsi changes were what was causing boot breakage.
Anyways, pulled this into arm-soc/fixes and it will be included with our
other misc. fixes for v4.6-rc.
Kevin
next prev parent reply other threads:[~2016-04-08 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 19:35 [GIT PULL] ARM: Amlogic: DT fix for v4.6-rc Carlo Caione
2016-04-08 23:24 ` Kevin Hilman [this message]
2016-04-10 10:03 ` Andreas Färber
2016-04-10 16:24 ` Carlo Caione
2016-04-11 23:39 ` Kevin Hilman
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=7hvb3rlm47.fsf@baylibre.com \
--to=khilman@baylibre$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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