From: Diederik de Haas <didi.debian@cknow.org>
To: Andy Yan <andyshrk@163.com>, linux-rockchip@lists.infradead.org
Cc: Heiko Stuebner <heiko@sntech.de>,
mripard@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
hjc@rock-chips.com, tzimmermann@suse.de,
dri-devel@lists.freedesktop.org, s.hauer@pengutronix.de,
Andy Yan <andy.yan@rock-chips.com>,
Heiko Stuebner <heiko@sntech.de>
Subject: Re: [PATCH 0/1] Fix the port mux of VP2
Date: Wed, 29 May 2024 17:55:25 +0200 [thread overview]
Message-ID: <2397969.FhQbyb98Gs@bagend> (raw)
In-Reply-To: <171405838036.2897712.4067984796758491640.b4-ty@sntech.de>
[-- Attachment #1.1: Type: text/plain, Size: 606 bytes --]
On Thursday, 25 April 2024 17:19:58 CEST Heiko Stuebner wrote:
> On Mon, 22 Apr 2024 18:19:04 +0800, Andy Yan wrote:
> > From: Andy Yan <andy.yan@rock-chips.com>
> >
> > The port mux bits of VP2 should be defined by
> > RK3568_OVL_PORT_SET__PORT2_MUX, this maybe a copy and paste error when
> > this driver first introduced.>
> > Hi Heiko:
> > Maybe thi is the problem you met when you porting the dsi2 driver.
> >
>
> Applied, thanks!
>
> [1/1] drm/rockchip: vop2: Fix the port mux of VP2
> commit: 2bdb481bf7a93c22b9fea8daefa2834aab23a70f
Wasn't this patch supposed to be part of 6.10-rc1?
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-05-29 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 10:19 [PATCH 0/1] Fix the port mux of VP2 Andy Yan
2024-04-22 10:19 ` [PATCH 1/1] drm/rockchip: vop2: " Andy Yan
2024-04-22 12:34 ` Sascha Hauer
2024-04-25 14:51 ` Heiko Stübner
2024-04-25 15:19 ` [PATCH 0/1] " Heiko Stuebner
2024-05-29 15:55 ` Diederik de Haas [this message]
2024-05-29 16:24 ` Heiko Stübner
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=2397969.FhQbyb98Gs@bagend \
--to=didi.debian@cknow.org \
--cc=andy.yan@rock-chips.com \
--cc=andyshrk@163.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mripard@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=tzimmermann@suse.de \
/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