linux-kernel - Re: [PATCH v2 56/57] docs: irqdomain: Update

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: <ec7e7166-6c02-4a2e-8b10-2c795304789d@kernel.org>
Date: Thu, 20 Mar 2025 07:32:35 +0100
From: Jiri Slaby <jirislaby@...nel.org>
To: Randy Dunlap <rdunlap@...radead.org>, tglx@...utronix.de
Cc: maz@...nel.org, linux-kernel@...r.kernel.org,
 Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org
Subject: Re: [PATCH v2 56/57] docs: irqdomain: Update

On 19. 03. 25, 19:01, Randy Dunlap wrote:
>> @@ -15,45 +15,64 @@ such as GPIO controllers avoid reimplementing identical callback
>>   mechanisms as the IRQ core system by modelling their interrupt
>>   handlers as irqchips. I.e. in effect cascading interrupt controllers.
>>   
>> -Here the interrupt number loose all kind of correspondence to
>> -hardware interrupt numbers: whereas in the past, IRQ numbers could
>> -be chosen so they matched the hardware IRQ line into the root
>> -interrupt controller (i.e. the component actually fireing the
>> -interrupt line to the CPU) nowadays this number is just a number.
>> +So in the past, IRQ numbers could be chosen so that they match the
>> +hardware IRQ line into the root interrupt controller (i.e. the
>> +component actually firing the interrupt line to the CPU). Nowadays,
>> +this number is just a number and the number loose all kind of
> 
>                                                 loses

Thanks, fixed in 55/57 where I explicitly do "3rd person -> add 's' to 
verbs.". Even though this was "loose" and not "lose" ;).

-- 
js
suse labs