linux-kernel - Re: [PATCH v2 05/24] media: iris: Allow substate transition to load resources during output streaming

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: <24714b00-cc15-4c9b-b0d4-8c76d702fcc2@nxsw.ie>
Date: Wed, 13 Aug 2025 21:51:51 +0000
From: Bryan O'Donoghue <bod.linux@...w.ie>
To: Dikshita Agarwal <quic_dikshita@...cinc.com>, Vikash Garodia <quic_vgarodia@...cinc.com>, Abhinav Kumar <abhinav.kumar@...ux.dev>, Bryan O'Donoghue <bryan.odonoghue@...aro.org>, Mauro Carvalho Chehab <mchehab@...nel.org>, Hans Verkuil <hverkuil@...all.nl>, Stefan Schmidt <stefan.schmidt@...aro.org>, Vedang Nagar <quic_vnagar@...cinc.com>
Cc: linux-media@...r.kernel.org, linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org, Renjiang Han <quic_renjiang@...cinc.com>, Wangao Wang <quic_wangaow@...cinc.com>
Subject: Re: [PATCH v2 05/24] media: iris: Allow substate transition to load resources during output streaming

On 13/08/2025 10:37, Dikshita Agarwal wrote:
> However, now after removing that restriction, the instance state can be
> OUTPUT_STREAMING when firmware start is triggered and substate needs to
> be moved to LOAD_RESOURCES.
> 
> Fixes: 547f7b8c5090 ("media: iris: add check to allow sub states transitions")

If a restriction has been removed, has that restriction been marked as a 
Fixes: ?

If not then we can't actually backport this fix as the dependency - the 
restriction removal has not been marked for backport.

Please evaluate if the necessary change you have stipulated here has 
been marked for backport with Fixes: and if so mention the appropriate 
commit SHA in your commit log.

If you are referring to the commit immediately preceding this patch "Fix 
buffer count reporting in internal buffer check" then again you should 
mention that in the log so _which_ dependency you mean is clear.

If I were trying to follow this series on some kind of -stable kernel, I 
don't think this commit log would reasonably tell me which depends I 
need as an antecedent.

---
bod