linux-kernel - Re: [PATCH] Fix typo in irq

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:   Tue, 27 Oct 2020 22:24:42 -0400
From:   Raphael Norwitz <raphael.s.norwitz@...il.com>
To:     Marc Zyngier <maz@...nel.org>
Cc:     Raphael Norwitz <raphael.norwitz@...anix.com>,
        linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
        Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH] Fix typo in irq_domain documentation

Ping - looks like this was never applied?

On Tue, Aug 25, 2020 at 6:23 AM Marc Zyngier <maz@...nel.org> wrote:
>
> On 2020-08-19 22:53, Raphael Norwitz wrote:
> > The irq_domain documentation states that "Here the interrupt number
> > loose all kind of correspondence to hardware interrupt numbers:...".
> > It's clear from the context that the author means to use "loses"
> > instead
> > of "loose". To avoid future confusion, this change fixes the
> > aforementioned wording.
> >
> > Signed-off-by: Raphael Norwitz <raphael.norwitz@...anix.com>
> > ---
> >  Documentation/core-api/irq/irq-domain.rst | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/core-api/irq/irq-domain.rst
> > b/Documentation/core-api/irq/irq-domain.rst
> > index 096db12..eba5e41 100644
> > --- a/Documentation/core-api/irq/irq-domain.rst
> > +++ b/Documentation/core-api/irq/irq-domain.rst
> > @@ -15,7 +15,7 @@ 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
> > +Here the interrupt number loses 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
>
> Acked-by: Marc Zyngier <maz@...nel.org>
>
>          M.
> --
> Jazz is not dead. It just smells funny...