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] [thread-next>] [day] [month] [year] [list]
Message-ID: <7c6ebf5f-ed13-46f3-88c8-a33205388d74@kernel.org>
Date: Fri, 6 Feb 2026 08:08:34 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Roger Shimizu <rosh@...ian.org>
Cc: Hongyang Zhao <hongyang.zhao@...ndersoft.com>,
 Andrzej Hajda <andrzej.hajda@...el.com>,
 Neil Armstrong <neil.armstrong@...aro.org>, Robert Foss <rfoss@...nel.org>,
 Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
 Jonas Karlman <jonas@...boo.se>, Jernej Skrabec <jernej.skrabec@...il.com>,
 David Airlie <airlied@...il.com>, Simona Vetter <simona@...ll.ch>,
 Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
 Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Vinod Koul <vkoul@...nel.org>,
 Bjorn Andersson <andersson@...nel.org>,
 Konrad Dybcio <konradybcio@...nel.org>, dri-devel@...ts.freedesktop.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v2 3/3] arm64: dts: qcom: qcs6490-rubikpi3: Use lt9611 DSI
 Port B

On 05/02/2026 20:36, Roger Shimizu wrote:
> On Thu, Feb 5, 2026 at 5:09 AM Krzysztof Kozlowski <krzk@...nel.org> wrote:
>>
>> On Wed, Jan 28, 2026 at 07:15:47PM +0800, Hongyang Zhao wrote:
>>> The LT9611 HDMI bridge on RubikPi3 has DSI physically connected to
>>> Port B. Update the devicetree to use port@1 which corresponds to
>>> Port B input on the LT9611.
>>>
>>> Signed-off-by: Hongyang Zhao <hongyang.zhao@...ndersoft.com>
>>> Reviewed-by: Roger Shimizu <rosh@...ian.org>
>>
>> Where did this happen?
>>
>> https://lore.kernel.org/all/?q=f%3Arosh%40debian.org
>>
>> And again, v1 was completely different so how pre-v1-internal-review
>> could be applied to this v2?
>>
>> Honestly, initial guidance is useful but continuous development behind
>> the closed doors is not.
> 
> FYI. v2 was updated per review feedback, which is public:
> https://lore.kernel.org/all/7d9041a3-9d2b-469a-9fa7-89d53bbd2a1f@linaro.org/

What? I asked about the tag. Do you understand how kernel review process
works?

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ