linux-kernel - Re: [PATCH] ARM: configs: stm32: Set CPU_V7M_NUM

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:   Fri, 31 Mar 2017 09:37:27 +0200
From:   Alexandre Torgue <alexandre.torgue@...com>
To:     Arnd Bergmann <arnd@...db.de>
CC:     Russell King <linux@...linux.org.uk>,
        Maxime Coquelin <mcoquelin.stm32@...il.com>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Olof Johansson <olof@...om.net>
Subject: Re: [PATCH] ARM: configs: stm32: Set CPU_V7M_NUM_IRQ to max value

Hi Arnd

On 03/30/2017 05:36 PM, Arnd Bergmann wrote:
> On Thu, Mar 23, 2017 at 11:09 AM, Alexandre TORGUE
> <alexandre.torgue@...com> wrote:
>> stm32_defconfig is used for several STM32 MCU: STM32F429, STM32F469,
>> STM32F746 and now STM32H743. Each of MCU listed have different interrupts
>> number mapped on NVIC. STM32F429: 81, STM32F469: 92, STM32F746: 97 and
>> STM32H743: 149. I could set CPU_V7M_NUM_IRQ to 149 but in order to avoid
>> forgetting to update this value for next STM32 MCU I prefer to set it to
>> max value: 240.
>>
>> Signed-off-by: Alexandre TORGUE <alexandre.torgue@...com>
>
> It's not entirely clear who you want to apply this (if any), given that you sent
> the patch to yourself. I've applied it to next/defconfig now, hope that's
> what you intended.

Actually, I pushed it mainly to share the patch and check comments. I 
planned to add it in my pull request, but no pb if you already took it :).

Regards
Alex

>
>       Arnd
>