[an error occurred while processing this directive]

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

[an error occurred while processing this directive]

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

Message-ID: <da22b26a-99da-4dae-9c46-2f871e45faa6@kernel.org>
Date: Thu, 21 Aug 2025 16:49:39 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Stephan Gerhold <stephan.gerhold@...aro.org>,
 Mukesh Ojha <mukesh.ojha@....qualcomm.com>
Cc: Bjorn Andersson <andersson@...nel.org>,
 Konrad Dybcio <konradybcio@...nel.org>,
 Vikash Garodia <quic_vgarodia@...cinc.com>,
 Dikshita Agarwal <quic_dikshita@...cinc.com>,
 Mauro Carvalho Chehab <mchehab@...nel.org>,
 Mathieu Poirier <mathieu.poirier@...aro.org>,
 Abhinav Kumar <abhinav.kumar@...ux.dev>,
 Bryan O'Donoghue <bryan.odonoghue@...aro.org>, linux-kernel@...r.kernel.org,
 linux-arm-msm@...r.kernel.org, linux-media@...r.kernel.org,
 linux-remoteproc@...r.kernel.org
Subject: Re: [PATCH v2 09/11] remoteproc: pas: Extend parse_fw callback to
 parse resource table

On 20/08/2025 10:36, Stephan Gerhold wrote:
>>  #include <linux/slab.h>
>>  #include <linux/soc/qcom/mdt_loader.h>
>>  
>> -#define MAX_RSCTABLE_SIZE	SZ_16K;
> 
> I'm confused why there is a semicolon here suddenly. Did you edit this
> patch by hand?
> 
> Applying: remoteproc: pas: Extend parse_fw callback to parse resource table
> Patch failed at 0009 remoteproc: pas: Extend parse_fw callback to parse resource table
> error: patch failed: drivers/soc/qcom/mdt_loader.c:22
> error: drivers/soc/qcom/mdt_loader.c: patch does not apply


This is very, very odd process. Editing patches POST format-patch or
post b4 (wut?) is a serious warning sign.

Few commit msgs also bring attention to possibility of AI, therefore
please clarify:

Did you use AI tools (qcom internal, external, any LLM/AI related tools)
when writing that code, formatting it or creating this patchset?

This is very important, as it create might create legal risk and
everyone should be aware of it.

Best regards,
Krzysztof