From: Jia Wang <wangjia@ultrarisc.com>
To: Linus Walleij <linusw@kernel.org>
Cc: wangjia@ultrarisc.com, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v4 0/2] pinctrl: ultrarisc: add DP1000 pinctrl support
Date: Fri, 12 Jun 2026 09:05:46 +0800 [thread overview]
Message-ID: <178122634683.2408461.10784730640588716167.b4-reply@b4> (raw)
In-Reply-To: <CAD++jL=m6++zOfq2gP4-y4N7U6nx1buVM5KMoxWJ_9PM6RVV8A@mail.gmail.com>
On 2026-06-11 14:24 +0200, Linus Walleij wrote:
> On Wed, Jun 10, 2026 at 7:29 AM Jia Wang via B4 Relay
> <devnull+wangjia.ultrarisc.com@kernel.org> wrote:
>
> > This series adds the devicetree schema and the pinctrl driver for the
> > DP1000 controller using generic pinctrl bindings.
> >
> > Compared with v1, this series is narrowed down to the pinctrl binding
> > and driver only. v1 patches 1, 2, 3, 5, 7, 8, and 9 (vendor prefix,
> > CPU/SoC bindings, DTS files, and defconfig update) are not included in
> > v2 and will be sent separately.
>
> This is a very good looking driver so I applied the patches!
>
> If there are any more snags they can certainly be fixed in-tree.
>
Hi Linus,
Thanks for applying the series!
> Yours,
> Linus Walleij
>
Best regards,
Jia Wang
prev parent reply other threads:[~2026-06-12 1:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 5:29 Jia Wang via B4 Relay
2026-06-10 5:29 ` [PATCH v4 1/2] dt-bindings: pinctrl: Add UltraRISC DP1000 pinctrl controller Jia Wang via B4 Relay
2026-06-10 5:29 ` [PATCH v4 2/2] pinctrl: ultrarisc: Add UltraRISC DP1000 pinctrl driver Jia Wang via B4 Relay
2026-06-10 7:16 ` Bartosz Golaszewski
2026-06-13 16:48 ` Nathan Chancellor
2026-06-15 5:53 ` Jia Wang
2026-06-11 12:24 ` [PATCH v4 0/2] pinctrl: ultrarisc: add DP1000 pinctrl support Linus Walleij
2026-06-12 1:05 ` Jia Wang [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=178122634683.2408461.10784730640588716167.b4-reply@b4 \
--to=wangjia@ultrarisc.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.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
all inboxes | Powered by JetHome®