From: khilman@baylibre•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/2] arm64: dts: mt7622: fix console output issue on rfb1
Date: Wed, 07 Nov 2018 07:48:45 -0800 [thread overview]
Message-ID: <7hr2fwevmq.fsf@baylibre.com> (raw)
In-Reply-To: <8043d487e7bd20a11b14d832702bda214a9a694f.1541566473.git.ryder.lee@mediatek.com> (Ryder Lee's message of "Wed, 7 Nov 2018 12:59:43 +0800")
Ryder Lee <ryder.lee@mediatek•com> writes:
> The issue was introduced by Kernel CI:
> https://kernelci.org/boot/id/5bbdcbad59b5146fc5b43592/
The issue was *found* by kernelCI, not introduced by kernelCI. ;)
> Fix this by using a 'stdout-path' property that points to the device.
>
> Fixes: c0d9f9ad4f76 ("arm64: dts: mt7622: add earlycon to mt7622-rfb1 board")
> Cc: stable at vger.kernel.org
> Signed-off-by: Ryder Lee <ryder.lee@mediatek•com>
Tested-by: Kevin Hilman <khilman@baylibre•com>
Note that this patch fixes the problem where there is no more console
output, but current mainline still doesn't boot as there's another
crash: http://termbin.com/zitb
Kevin
prev parent reply other threads:[~2018-11-07 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 4:59 [PATCH 1/2] arm64: dts: mt7622: fix console output issue on rfb1 Ryder Lee
2018-11-07 4:59 ` [PATCH 2/2] arm64: dts: mt7622: fix console output issue on BPI-R64 board Ryder Lee
2018-11-07 15:48 ` Kevin Hilman [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=7hr2fwevmq.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