From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: stable@vger.kernel.org,
Peri-Dev <oss-upstream-dev@lm.renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Tong Duc Duy <duy.tong-duc@banvien.com.vn>,
Thuan Nguyen <thuan.nguyen-hong@banvien.com.vn>,
Duy Nguyen <duy.nguyen.rh@renesas.com>,
Chu Quoc Khanh <khanh.chu@banvien.com.vn>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Subject: Re: [Renesas Linux Kernel Test Report] DU/Device Tree: Missing pin control for DSI-eDP IRQ
Date: Mon, 13 Apr 2026 12:46:13 +0200 [thread overview]
Message-ID: <2026041351-skyward-constrain-e6e2@gregkh> (raw)
In-Reply-To: <87lder39bh.wl-kuninori.morimoto.gx@renesas.com>
On Mon, Apr 13, 2026 at 02:04:02AM +0000, Kuninori Morimoto wrote:
>
> Hi Greg
> Cc Geert, Laurent
>
> Linux LTS v6.6 / v6.12 backported this commit
>
> 9133bc3f0564890218cbba6cc7e81ebc0841a6f1
> ("drm/bridge: ti-sn65dsi86: Add support for DisplayPort mode with HPD")
>
> Because of that, Renesas needs this commit.
>
> 8219a455efd4ba11c1d30c1bbc9ce853466c19bf
> ("arm64: dts: renesas: white-hawk-cpu-common:
> Add pin control for DSI-eDP IRQ")
>
> Could you please backport it too ?
It does not apply properly to 6.6.y or 6.1.y, so can you provide working
backports there?
I've added it to 6.12.y now.
thanks,
greg k-h
next prev parent reply other threads:[~2026-04-13 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PUZPR03MB71159178A9463AF8E5C1B4709F582@PUZPR03MB7115.apcprd03.prod.outlook.com>
[not found] ` <87wlyfeks1.wl-kuninori.morimoto.gx@renesas.com>
[not found] ` <20260410085604.GD2712636@killaraus.ideasonboard.com>
2026-04-13 2:04 ` [Renesas Linux Kernel Test Report] DU/Device Tree: Missing pin control for DSI-eDP IRQ Kuninori Morimoto
2026-04-13 10:46 ` Greg Kroah-Hartman [this message]
2026-04-13 11:19 ` Geert Uytterhoeven
2026-04-14 23:36 ` Kuninori Morimoto
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=2026041351-skyward-constrain-e6e2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=duy.nguyen.rh@renesas.com \
--cc=duy.tong-duc@banvien.com.vn \
--cc=geert+renesas@glider.be \
--cc=khanh.chu@banvien.com.vn \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=oss-upstream-dev@lm.renesas.com \
--cc=stable@vger.kernel.org \
--cc=thuan.nguyen-hong@banvien.com.vn \
--cc=tomi.valkeinen@ideasonboard.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