[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240802-rippling-clubbing-5318f914f16a@spud>
Date: Fri, 2 Aug 2024 09:08:32 +0100
From: Conor Dooley <conor@...nel.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Conor Dooley <conor.dooley@...rochip.com>, linux-kernel@...r.kernel.org,
Marc Zyngier <maz@...nel.org>,
Daire McNamara <daire.mcnamara@...rochip.com>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
linux-riscv@...ts.infradead.org, linux-gpio@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [RFC v7 3/6] irqchip: add mpfs gpio interrupt mux
On Thu, Aug 01, 2024 at 08:49:08PM +0200, Thomas Gleixner wrote:
> On Thu, Aug 01 2024 at 16:09, Conor Dooley wrote:
> > On Mon, Jul 29, 2024 at 12:41:25PM +0200, Thomas Gleixner wrote:
> >> > + /*
> >> > + * If a bit is set in the mux, GPIO the corresponding interrupt from
> >> > + * controller 2 is direct and that controllers 0 or 1 is muxed.
> >>
> >> This is not a coherent sentence.
> >
> > It should read "controller 0 or 1;s interrupt is muxed". Does that make
Heh, I even typoed here, the ; should be a '.
> > more sense to you?
>
> No: If a bit is set in the mux, GPIO the corresponding...
>
> I'm already failing at 'GPIO'. My parser expects a verb there :)
Ah, so double mistake in the sentence. s/GPIO// I suppose. An updated
comment could be:
"If a bit is set in the mux, the corresponding interrupt from GPIO
controller 2 is direct and controller 0 or 1's interrupt is muxed"
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists