From: Conor Dooley <conor@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org,
Valentina.FernandezAlanis@microchip.com
Subject: Re: [PATCH v2 0/5] Microchip mpfs/pic64gx pinctrl
Date: Tue, 21 Oct 2025 10:47:30 +0100 [thread overview]
Message-ID: <20251021-distaste-antelope-d7354c0c35c0@spud> (raw)
In-Reply-To: <CACRpkdadawJmrED-dPpnm+MKD1ndt4V86GOebkiQzU=d+-vHjA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
On Mon, Oct 20, 2025 at 11:05:53PM +0200, Linus Walleij wrote:
> On Tue, Oct 14, 2025 at 4:36 PM Conor Dooley <conor@kernel.org> wrote:
>
> > From: Conor Dooley <conor.dooley@microchip.com>
>
> > Following from my RFC recently [0] I've got a v2 here that's implemented
> > the change from using the pinmux property to using functions and groups
> > that you asked for Linus.
>
> Overall I'm very happy with what I see, I see there are some comments
> and my only comment would be to add
>
> depends on ARCH_MICROCHIP || COMPILE_TEST
>
> on the drivers so they get some proper compile testing, and I expect
> we can apply v3.
Oh, that's a silly one to forget about. I'll do that and just delete the
TODO line that I had in there, since you've not objected to the macro
use.
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-10-21 9:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 14:35 [PATCH v2 0/5] Microchip mpfs/pic64gx pinctrl Conor Dooley
2025-10-14 14:35 ` [PATCH v2 1/5] dt-bindings: pinctrl: document pic64gx "gpio2" pinmux Conor Dooley
2025-10-20 21:01 ` Rob Herring (Arm)
2025-10-14 14:35 ` [PATCH v2 2/5] pinctrl: add pic64gx "gpio2" pinmux driver Conor Dooley
2025-10-14 14:35 ` [PATCH v2 3/5] dt-bindings: pinctrl: document polarfire soc iomux0 pinmux Conor Dooley
2025-10-20 21:01 ` Rob Herring (Arm)
2025-10-14 14:35 ` [PATCH v2 4/5] pinctrl: add polarfire soc iomux0 pinmux driver Conor Dooley
2025-10-14 14:53 ` Conor Dooley
2025-10-14 14:35 ` [PATCH v2 5/5] MAINTAINERS: add Microchip RISC-V pinctrl drivers/bindings to entry Conor Dooley
2025-10-20 21:05 ` [PATCH v2 0/5] Microchip mpfs/pic64gx pinctrl Linus Walleij
2025-10-21 9:47 ` Conor Dooley [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=20251021-distaste-antelope-d7354c0c35c0@spud \
--to=conor@kernel.org \
--cc=Valentina.FernandezAlanis@microchip.com \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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).