From: Krzysztof Kozlowski <krzk@kernel.org>
To: Billy Tsai <billy_tsai@aspeedtech.com>
Cc: lee@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, joel@jms.id.au,
andrew@codeconstruct.com.au, linus.walleij@linaro.org,
brgl@bgdev.pl, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
openbmc@lists.ozlabs.org, linux-gpio@vger.kernel.org,
BMC-SW@aspeedtech.com
Subject: Re: [PATCH v2 0/4] Add pinctrl support for AST2700 SoC
Date: Fri, 5 Sep 2025 10:12:00 +0200 [thread overview]
Message-ID: <20250905-rough-notorious-leech-dd7a0d@kuoka> (raw)
In-Reply-To: <20250904103401.88287-1-billy_tsai@aspeedtech.com>
On Thu, Sep 04, 2025 at 06:33:57PM +0800, Billy Tsai wrote:
> Document and add the pinctrl driver for AST2700 SoC.
>
> Changes since v1:
> - Update pinctrl aspeed binding files.
Anything is an update.
Really too vague and some time ago I am sure I complained about this to
Aspeed.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-09-05 9:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 10:33 [PATCH v2 0/4] Add pinctrl support for AST2700 SoC Billy Tsai
2025-09-04 10:33 ` [PATCH v2 1/4] dt-bindings: mfd: aspeed,ast2x00-scu: Support ast2700 pinctrl Billy Tsai
2025-09-05 8:13 ` Krzysztof Kozlowski
2025-09-04 10:33 ` [PATCH v2 2/4] dt-bindings: pinctrl: aspeed: Add support for AST27xx Billy Tsai
2025-09-05 8:16 ` Krzysztof Kozlowski
2025-09-04 10:34 ` [PATCH v2 4/4] arm64: dts: add AST27xx pinctrl configuration nodes Billy Tsai
2025-09-04 14:26 ` Rob Herring
2025-09-05 8:12 ` Krzysztof Kozlowski [this message]
[not found] ` <20250904103401.88287-4-billy_tsai@aspeedtech.com>
2025-09-06 15:59 ` [PATCH v2 3/4] pinctrl: aspeed: Add AST2700 pinmux support kernel test robot
2025-09-25 4:48 ` Andrew Jeffery
2025-11-11 2:24 ` Billy Tsai
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=20250905-rough-notorious-leech-dd7a0d@kuoka \
--to=krzk@kernel.org \
--cc=BMC-SW@aspeedtech.com \
--cc=andrew@codeconstruct.com.au \
--cc=billy_tsai@aspeedtech.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.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