From: "Uwe Kleine-König" <ukleinek@kernel.org>
To: Yixun Lan <dlan@kernel.org>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Duje Mihanović" <duje@dujemihanovic.xyz>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev
Subject: Re: [PATCH v2 0/2] pwm: spacemit: Add Support for K3 SoC
Date: Fri, 15 May 2026 10:59:56 +0200 [thread overview]
Message-ID: <agbgG00YENm388dd@monoceros> (raw)
In-Reply-To: <20260514233448-GKA3663945@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
On Thu, May 14, 2026 at 11:34:48PM +0000, Yixun Lan wrote:
> Hi Uwe Kleine-König,
> Can you queue this one for v7.2? I'm sending the DTS part patch
> and got a complaint for "clock definitions violation"
I applied it to
https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git pwm/for-next
now.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Uwe Kleine-König" <ukleinek@kernel.org>
To: Yixun Lan <dlan@kernel.org>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Duje Mihanović" <duje@dujemihanovic.xyz>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev
Subject: Re: [PATCH v2 0/2] pwm: spacemit: Add Support for K3 SoC
Date: Fri, 15 May 2026 10:59:56 +0200 [thread overview]
Message-ID: <agbgG00YENm388dd@monoceros> (raw)
In-Reply-To: <20260514233448-GKA3663945@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 341 bytes --]
On Thu, May 14, 2026 at 11:34:48PM +0000, Yixun Lan wrote:
> Hi Uwe Kleine-König,
> Can you queue this one for v7.2? I'm sending the DTS part patch
> and got a complaint for "clock definitions violation"
I applied it to
https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git pwm/for-next
now.
Best regards
Uwe
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-05-15 8:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 10:46 [PATCH v2 0/2] pwm: spacemit: Add Support for K3 SoC Yixun Lan
2026-04-28 10:46 ` Yixun Lan
2026-04-28 10:46 ` [PATCH v2 1/2] dt-bindings: pwm: marvell,pxa-pwm: Add SpacemiT K3 PWM support Yixun Lan
2026-04-28 10:46 ` Yixun Lan
2026-04-28 18:12 ` Conor Dooley
2026-04-28 18:12 ` Conor Dooley
2026-04-28 10:46 ` [PATCH v2 2/2] pwm: pxa: Add optional bus clock Yixun Lan
2026-04-28 10:46 ` Yixun Lan
2026-05-14 23:34 ` [PATCH v2 0/2] pwm: spacemit: Add Support for K3 SoC Yixun Lan
2026-05-14 23:34 ` Yixun Lan
2026-05-15 8:59 ` Uwe Kleine-König [this message]
2026-05-15 8:59 ` Uwe Kleine-König
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=agbgG00YENm388dd@monoceros \
--to=ukleinek@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@kernel.org \
--cc=duje@dujemihanovic.xyz \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.