public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luca Ceresoli" <luca.ceresoli@bootlin.com>
To: "Cristian Ciocaltea" <cristian.ciocaltea@collabora.com>,
	"Christian Hewitt" <christianshewitt@gmail.com>
Cc: "Andrzej Hajda" <andrzej.hajda@intel.com>,
	"Neil Armstrong" <neil.armstrong@linaro.org>,
	"Robert Foss" <rfoss@kernel.org>,
	"Laurent Pinchart" <Laurent.pinchart@ideasonboard.com>,
	"Jonas Karlman" <jonas@kwiboo.se>,
	"Jernej Skrabec" <jernej.skrabec@gmail.com>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
	"Detlev Casanova" <detlev.casanova@collabora.com>,
	"Douglas Anderson" <dianders@chromium.org>,
	"Andy Yan" <andy.yan@rock-chips.com>,
	"Sugar Zhang" <sugar.zhang@rock-chips.com>,
	"Heiko Stuebner" <heiko@sntech.de>,
	<dri-devel@lists.freedesktop.org>,
	<linux-rockchip@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] drm/bridge: dw-hdmi-qp: fix multi-channel audio output
Date: Wed, 18 Mar 2026 22:52:26 +0100	[thread overview]
Message-ID: <DH68P6XTTTTP.10WUEJQMP1OC9@bootlin.com> (raw)
In-Reply-To: <0895dfa0-9527-41b1-b991-a2bd6e0c549b@collabora.com>

Hello Cristian,

On Wed Mar 18, 2026 at 7:12 PM CET, Cristian Ciocaltea wrote:
>> So now this patch is on drm-misc-fixes, but drm-misc-fixes and
>> drm-misc-next are now conflicting because of other changes by Cristian
>> Ciocaltea applied in the meanwhile to drm-misc-next, and particularly
>> commit 3ea699b56d31 ("drm/bridge: dw-hdmi-qp: Rework Audio InfoFrame
>> handler").
>>
>> Cristian, Christian (heh), Jonas, could you please check whether the code
>> on drm-misc-next has or not the bug that is fixed here? And if it still
>> has, send a fix based on current drm-misc-next?
>
> The conflicting commit in drm-misc-next (i.e. 3ea699b56d31) implicitly resolves
> this audio related issue as well, hence there is no need for any further action.

Good to know! Thanks for checking.

Luca

--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2026-03-18 21:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-28 11:28 [PATCH v2] drm/bridge: dw-hdmi-qp: fix multi-channel audio output Christian Hewitt
2026-03-17 16:16 ` Luca Ceresoli
2026-03-17 16:49   ` Christian Hewitt
2026-03-17 17:35     ` Luca Ceresoli
2026-03-18 18:12       ` Cristian Ciocaltea
2026-03-18 21:52         ` Luca Ceresoli [this message]
2026-03-17 17:29 ` Luca Ceresoli

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=DH68P6XTTTTP.10WUEJQMP1OC9@bootlin.com \
    --to=luca.ceresoli@bootlin.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=andy.yan@rock-chips.com \
    --cc=christianshewitt@gmail.com \
    --cc=cristian.ciocaltea@collabora.com \
    --cc=detlev.casanova@collabora.com \
    --cc=dianders@chromium.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=heiko@sntech.de \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rfoss@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=sugar.zhang@rock-chips.com \
    --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