From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] i.MX fixes for 4.19
Date: Wed, 29 Aug 2018 11:50:04 -0700 [thread overview]
Message-ID: <20180829185004.a2jvj3cdqujxllft@localhost> (raw)
In-Reply-To: <20180827091056.GN3850@dragon>
Hi,
On Mon, Aug 27, 2018 at 05:10:58PM +0800, Shawn Guo wrote:
> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>
> Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-fixes-4.19
>
> for you to fetch changes up to b9543a2e39dc909e6b7ec901b6c7208d01d5c0dd:
>
> ARM: imx_v6_v7_defconfig: Select CONFIG_DRM_PANEL_SEIKO_43WVF1G (2018-08-27 15:05:48 +0800)
>
> ----------------------------------------------------------------
> i.MX fixes for 4.19:
> - i.MX display folks decided to switch MXS display driver from legacy
> FB to DRM during 4.19 merge window. It leads to a fallout on some
> Freescale/NXP development boards with Seiko 43WVF1G panel, because
> this DRM panel driver is not enabled in i.MX defconfig. Here is
> a series from Fabio to convert i.MX23/28 EVK DT to Seiko 43WVF1G
> panel bindings and enable the panel driver in i.MX defconfig, so that
> users can still get functional LCD on these boards by default.
This would have been nice to catch with -next, especially since it was found so
quickly after the merge window closed (that way we could have kept the period
of breakage much shorter).
> - A fix from Leonard to revert incorrect legacy PCI irq mapping in
> i.MX7 device tree, that was caused by document errors.
Merged this branch, thanks!
-Olof
next prev parent reply other threads:[~2018-08-29 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 9:10 [GIT PULL] i.MX fixes for 4.19 Shawn Guo
2018-08-29 18:50 ` Olof Johansson [this message]
2018-08-30 0:34 ` Shawn Guo
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=20180829185004.a2jvj3cdqujxllft@localhost \
--to=olof@lixom.net \
--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 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.