From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH v5 0/4] Add missing port pins for RZ/Five SoC
Date: Mon, 29 Jan 2024 09:25:37 +0100 [thread overview]
Message-ID: <CAMuHMdWKvJRFP+zOeWPALbYwAf7Z_UW879q1aLXyFwXqaJp9GA@mail.gmail.com> (raw)
In-Reply-To: <CA+V-a8t4v2CxZWrLRKBinS5fyG-_FzDFz5zA=mgcrNutJABr5g@mail.gmail.com>
Hi Prabhakar,
On Mon, Jan 29, 2024 at 9:16 AM Lad, Prabhakar
<prabhakar.csengg@gmail.com> wrote:
> On Mon, Jan 15, 2024 at 1:08 PM Prabhakar <prabhakar.csengg@gmail.com> wrote:
> > From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> > This patch series intends to incorporate the absent port pins P19 to P28,
> > which are exclusively available on the RZ/Five SoC.
> >
> > Cheers,
> > Prabhakar
> >
> > v4 -> v5:
> > * Made struct rzg2l_variable_pin_cfg variables u32
> > * Updated PIN_CFG_PIN_MAP_MASK macro to use GENMASK_ULL() as reported
> > by kernel test robot.
> > Lad Prabhakar (4):
> > pinctrl: renesas: rzg2l: Improve code for readability
> > pinctrl: renesas: rzg2l: Include pinmap in RZG2L_GPIO_PORT_PACK()
> > macro
> > pinctrl: renesas: pinctrl-rzg2l: Add the missing port pins P19 to P28
> > riscv: dts: renesas: r9a07g043f: Update gpio-ranges property
> >
> > arch/riscv/boot/dts/renesas/r9a07g043f.dtsi | 4 +
> > drivers/pinctrl/renesas/pinctrl-rzg2l.c | 284 +++++++++++++++++---
> > 2 files changed, 248 insertions(+), 40 deletions(-)
> >
> With recent changes to pinctrl-rzg2l.c this patch series (patch #2)
> does not apply cleanly anymore. Shall I resend it?
Yes please. That would save me from resolving the conflict when
I get to this series.
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2024-01-29 8:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 13:08 [PATCH v5 0/4] Add missing port pins for RZ/Five SoC Prabhakar
2024-01-15 13:08 ` [PATCH v5 1/4] pinctrl: renesas: rzg2l: Improve code for readability Prabhakar
2024-01-15 13:08 ` [PATCH v5 2/4] pinctrl: renesas: rzg2l: Include pinmap in RZG2L_GPIO_PORT_PACK() macro Prabhakar
2024-01-15 13:08 ` [PATCH v5 3/4] pinctrl: renesas: pinctrl-rzg2l: Add the missing port pins P19 to P28 Prabhakar
2024-01-15 13:08 ` [PATCH v5 4/4] riscv: dts: renesas: r9a07g043f: Update gpio-ranges property Prabhakar
2024-01-15 14:07 ` Geert Uytterhoeven
2024-01-29 8:15 ` [PATCH v5 0/4] Add missing port pins for RZ/Five SoC Lad, Prabhakar
2024-01-29 8:25 ` Geert Uytterhoeven [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMuHMdWKvJRFP+zOeWPALbYwAf7Z_UW879q1aLXyFwXqaJp9GA@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).