linux-kernel - Re: [V1 2/2] drivers soc: add support for ST stm32mp13xx family

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 for Android: free password hash cracker in your pocket

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

Message-ID: <a33548d2-040d-4a51-8fc3-ce3042ce4a24@enneenne.com>
Date: Mon, 26 May 2025 12:56:20 +0200
From: Rodolfo Giometti <giometti@...eenne.com>
To: Alexandre TORGUE <alexandre.torgue@...s.st.com>
Cc: Maxime Coquelin <mcoquelin.stm32@...il.com>,
 Eric Fourmont <eric.fourmont-ext@...com>,
 Yann GAUTIER <yann.gautier@...s.st.com>, linux-kernel@...r.kernel.org
Subject: Re: [V1 2/2] drivers soc: add support for ST stm32mp13xx family

On 20/05/25 10:55, Alexandre TORGUE wrote:
> hi
> 
> On 5/19/25 15:08, Rodolfo Giometti wrote:
>> This patch adds SoC support for the ST stm32mp13xx family. It also
>> adds the special attribute "secure" which returns the CPU's secure
>> mode status.
>>
>> Signed-off-by: Rodolfo Giometti <giometti@...eenne.com>
>> ---
>>   drivers/soc/st/Makefile        |   1 +
>>   drivers/soc/st/soc-stm32mp13.c | 253 +++++++++++++++++++++++++++++++++
>>   2 files changed, 254 insertions(+)
>>   create mode 100644 drivers/soc/st/soc-stm32mp13.c
>>
>> diff --git a/drivers/soc/st/Makefile b/drivers/soc/st/Makefile
>> index 6c71607f6c89..c84bf510928d 100644
>> --- a/drivers/soc/st/Makefile
>> +++ b/drivers/soc/st/Makefile
>> @@ -1,3 +1,4 @@
>>   obj-$(CONFIG_STM32_PM_DOMAINS) += stm32_pm_domain.o
>>   obj-$(CONFIG_STM32_RISAB) += stm32_risab.o
>>   obj-$(CONFIG_STM32_RISAF) += stm32_risaf.o
>> +obj-$(CONFIG_MACH_STM32MP13) += soc-stm32mp13.o
> 
> Your patch does not applied because the file does not exist. You can't take a 
> patch on our github, push it as it is without rebase it on mainline kernel.
OK, my patch set doesn't apply to the vanilla kernel, and I'm going to remove 
linux-kernel@...r.kernel.org from the recipients list.

Stated this, where should I send my patches? Would the 
linux-stm32@...md-mailman.stormreply.com list be a suitable candidate? :)

Ciao,

Rodolfo

-- 
GNU/Linux Solutions                  e-mail: giometti@...eenne.com
Linux Device Driver                          giometti@...ux.it
Embedded Systems                     phone:  +39 349 2432127
UNIX programming