From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
To: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Cc: Biju Das <biju.das.jz@bp.renesas.com>
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] drm: rcar-du: Fix LVDS dual link mode kernel crash
Date: Mon, 21 Sep 2020 12:54:52 +0000 [thread overview]
Message-ID: <20200921125453.222E1218AC@mail.kernel.org> (raw)
In-Reply-To: <20200918110818.11303-1-biju.das.jz@bp.renesas.com>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: a6cc417d3eee ("drm: rcar-du: Turn LVDS clock output on/off for DPAD0 output on D3/E3").
The bot has tested the following trees: v5.8.10, v5.4.66.
v5.8.10: Build OK!
v5.4.66: Failed to apply! Possible dependencies:
35a61fe9218a ("drm: Stop accessing encoder->bridge directly")
62afb4ad425a ("drm/connector: Allow max possible encoders to attach to a connector")
89958b7cd955 ("drm/bridge: panel: Infer connector type from panel by default")
a92462d6bf49 ("drm/connector: Share with non-atomic drivers the function to get the single encoder")
ea099adfdf4b ("drm/bridge: Rename bridge helpers targeting a bridge chain")
fadf872d9d92 ("drm/bridge: Introduce drm_bridge_get_next_bridge()")
fe9e557dfb48 ("drm/bridge: Fix references to drm_bridge_funcs in documentation")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
prev parent reply other threads:[~2020-09-21 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 11:08 [PATCH] drm: rcar-du: Fix LVDS dual link mode kernel crash Biju Das
2020-09-18 11:08 ` Biju Das
2020-09-21 12:54 ` Sasha Levin [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=20200921125453.222E1218AC@mail.kernel.org \
--to=sashal@kernel.org \
--cc=biju.das.jz@bp.renesas.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.