From: Fabio Estevam <festevam@gmail.com>
To: Robert Foss <robert.foss@collabora.com>
Cc: Gary Bisson <gary.bisson@boundarydevices.com>,
Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Fabio Estevam <festevam@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
Troy Kisky <troy.kisky@boundarydevices.com>,
Rob Herring <robh+dt@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: dts: imx6qdl-nitrogen6_max: Disable LVDS channels
Date: Wed, 10 Apr 2019 09:00:07 -0300 [thread overview]
Message-ID: <CAOMZO5Dfyu3AvQ9gD+PXCFE=PG9O1Q+0oRE=rM21nTriJpTzog@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5Aj+NKOsa1zXfQqsSzqDJGOcza+1wGjdiEytvjAhsnOVQ@mail.gmail.com>
On Wed, Apr 10, 2019 at 8:55 AM Fabio Estevam <festevam@gmail.com> wrote:
> Please check if this patch fixes the problem on your case:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20190410&id=728e096dd70889c2e80dd4153feee91afb1daf72
Also, just confirmed that this commit reached 5.1-rc3.
Robert, please run 5.1-rc3 (or rc4) and let us know if you still see
the problem.
prev parent reply other threads:[~2019-04-10 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 17:53 [PATCH] ARM: dts: imx6qdl-nitrogen6_max: Disable LVDS channels Robert Foss
2019-04-08 20:37 ` Fabio Estevam
2019-04-09 0:07 ` Robert Foss
2019-04-10 7:35 ` Gary Bisson
2019-04-10 10:57 ` Robert Foss
2019-04-10 11:55 ` Fabio Estevam
2019-04-10 12:00 ` Fabio Estevam [this message]
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='CAOMZO5Dfyu3AvQ9gD+PXCFE=PG9O1Q+0oRE=rM21nTriJpTzog@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=gary.bisson@boundarydevices.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robert.foss@collabora.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=troy.kisky@boundarydevices.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 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).