linux-kernel - Re: [PATCH v3 4/4] ARM: configs: at91: Enable LVDS serializer support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Tue, 20 Feb 2024 08:50:46 +0000
From: <Dharma.B@...rochip.com>
To: <krzysztof.kozlowski@...aro.org>, <andrzej.hajda@...el.com>,
	<neil.armstrong@...aro.org>, <rfoss@...nel.org>,
	<Laurent.pinchart@...asonboard.com>, <jonas@...boo.se>,
	<jernej.skrabec@...il.com>, <maarten.lankhorst@...ux.intel.com>,
	<mripard@...nel.org>, <tzimmermann@...e.de>, <airlied@...il.com>,
	<daniel@...ll.ch>, <robh+dt@...nel.org>, <krzysztof.kozlowski+dt@...aro.org>,
	<conor+dt@...nel.org>, <Manikandan.M@...rochip.com>,
	<linux-kernel@...r.kernel.org>, <dri-devel@...ts.freedesktop.org>,
	<linux@...linux.org.uk>, <Nicolas.Ferre@...rochip.com>,
	<alexandre.belloni@...tlin.com>, <claudiu.beznea@...on.dev>,
	<geert+renesas@...der.be>, <arnd@...db.de>, <palmer@...osinc.com>,
	<akpm@...ux-foundation.org>, <gerg@...ux-m68k.org>, <rdunlap@...radead.org>,
	<vbabka@...e.cz>, <linux-arm-kernel@...ts.infradead.org>
CC: <Hari.PrasathGE@...rochip.com>
Subject: Re: [PATCH v3 4/4] ARM: configs: at91: Enable LVDS serializer support

Hi Krzysztof,

On 20/02/24 2:15 pm, Krzysztof Kozlowski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On 07/02/2024 11:28, Dharma Balasubiramani wrote:
>> Enable LVDS serializer support for display pipeline.
>>
>> Signed-off-by: Dharma Balasubiramani <dharma.b@...rochip.com>
>> Acked-by: Hari Prasath Gujulan Elango <hari.prasathge@...rochip.com>
>> Acked-by: Nicolas Ferre <nicolas.ferre@...rochip.com>
>> ---
>> Changelog
>> v2 -> v3
>> - No Changes.
>> ---
> 
> In other email thread you mentioned that this depends on driver changes,
> while that's only partially correct. This patch does not make sense if
> others are not accepted, but the others are not dependency for this one.
> This should go via arm soc.
> 
> In the future, please state clearly dependencies in cover letter or each
> patch changelog (so ---, not commit msg).

Understood, Thanks for the comprehensive explanation. I will take care 
of this in future.

> 
> Best regards,
> Krzysztof
> 

-- 
With Best Regards,
Dharma B.