On Mon, Nov 21, 2022 at 4:51 PM Geert Uytterhoeven <geert+renesas@xxxxxxxxx> wrote: > Use the existing variable "gpio", instead of obtaining the hwirq number > again. > > Signed-off-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> Patch applied. Yours, Linus Walleij
Re: [PATCH resend] pinctrl: starfive: Use existing variable gpio
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH resend] pinctrl: starfive: Use existing variable gpio
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Tue, 22 Nov 2022 09:25:52 +0100
- In-reply-to: <3b6b8597792a393d0f21b8489dd933663dfd2b90.1669045778.git.geert+renesas@glider.be>
- References: <3b6b8597792a393d0f21b8489dd933663dfd2b90.1669045778.git.geert+renesas@glider.be>
- References:
- [PATCH resend] pinctrl: starfive: Use existing variable gpio
- From: Geert Uytterhoeven
- [PATCH resend] pinctrl: starfive: Use existing variable gpio
- Prev by Date: Re: [PATCH] dt-bindings: pinctrl: semtech,sx150xq: fix match patterns for 16 GPIOs matching
- Next by Date: [PATCH linux-next] pinctrl: qcom: remove duplicate included header files
- Previous by thread: Re: [PATCH resend] pinctrl: starfive: Use existing variable gpio
- Next by thread: [linusw-pinctrl:for-next] BUILD SUCCESS b6b904083dfcffadc06928b46f7a6416beba0031
- Index(es):
 |