From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Mark Brown <broonie@kernel.org>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
Thomas Lin <thomas_lin@lecomputing.com>,
rafael@kernel.org, lenb@kernel.org, hoan@os.amperecomputing.com,
linusw@kernel.org, mika.westerberg@linux.intel.com,
andriy.shevchenko@linux.intel.com, jsd@semihalf.com,
andi.shyti@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-spi@vger.kernel.org,
lucas_hao@lecomputing.com, puntar_liu@lecomputing.com,
jihua_tao@lecomputing.com, stan_xu@lecomputing.com,
lumin_liu@lecomputing.com, notics_zhang@lecomputing.com,
braden_zhang@lecomputing.com, harold_wu@lecomputing.com,
will_zhang@lecomputing.com, aurora_jiang@lecomputing.com,
ryen_lin@lecomputing.com, andy_jiang@lecomputing.com
Subject: Re: [PATCH v4 1/3] gpio: dwapb: Add ACPI ID LECA0001 for LECARC SoCs
Date: Wed, 20 May 2026 19:11:38 +0200 [thread overview]
Message-ID: <ag3rSq-gx5bruPNW@shikoro> (raw)
In-Reply-To: <cc8dc59e-fc00-4f7b-9f24-467c670c5615@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
On Wed, May 20, 2026 at 04:24:12PM +0100, Mark Brown wrote:
> On Wed, May 20, 2026 at 05:15:12PM +0200, Bartosz Golaszewski wrote:
>
> > I'm not sure about how to interpret the cover letter - is it fine to
> > take this independently through the GPIO tree for v7.2?
>
> AFAICT any dependency that exists is runtime only, it's just a bunch of
> quirks and none of the patches touch header files.
Patch 3 depends on patch 2. So, maybe it can go all in via GPIO?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-05-20 17:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 8:11 [PATCH v4 0/3] arm64: Add LECARC ACPI IDs for DesignWare GPIO, SPI, I2C Thomas Lin
2026-05-20 8:11 ` [PATCH v4 1/3] gpio: dwapb: Add ACPI ID LECA0001 for LECARC SoCs Thomas Lin
2026-05-20 15:15 ` Bartosz Golaszewski
2026-05-20 15:24 ` Mark Brown
2026-05-20 17:11 ` Wolfram Sang [this message]
2026-05-20 17:15 ` Mark Brown
2026-05-20 8:11 ` [PATCH v4 2/3] spi: dw-mmio: Add ACPI ID LECA0002 " Thomas Lin
2026-05-20 17:27 ` Mark Brown
2026-05-20 8:11 ` [PATCH v4 3/3] i2c: designware: Add ACPI ID LECA0003 " Thomas Lin
2026-05-20 14:17 ` Wolfram Sang
2026-06-05 0:07 ` Andi Shyti
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=ag3rSq-gx5bruPNW@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy_jiang@lecomputing.com \
--cc=aurora_jiang@lecomputing.com \
--cc=braden_zhang@lecomputing.com \
--cc=brgl@kernel.org \
--cc=broonie@kernel.org \
--cc=harold_wu@lecomputing.com \
--cc=hoan@os.amperecomputing.com \
--cc=jihua_tao@lecomputing.com \
--cc=jsd@semihalf.com \
--cc=lenb@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lucas_hao@lecomputing.com \
--cc=lumin_liu@lecomputing.com \
--cc=mika.westerberg@linux.intel.com \
--cc=notics_zhang@lecomputing.com \
--cc=puntar_liu@lecomputing.com \
--cc=rafael@kernel.org \
--cc=ryen_lin@lecomputing.com \
--cc=stan_xu@lecomputing.com \
--cc=thomas_lin@lecomputing.com \
--cc=will_zhang@lecomputing.com \
/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