From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "André Draszik" <andre.draszik@linaro.org>,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
alim.akhtar@samsung.com, peter.griffin@linaro.org
Cc: kernel-team@android.com, tudor.ambarus@linaro.org,
willmcvicker@google.com, daniel.lezcano@linaro.org,
tglx@linutronix.de, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: exynos: gs101: sysreg_peric1 needs a clock
Date: Fri, 26 Jan 2024 11:35:48 +0100 [thread overview]
Message-ID: <58ba835e-46d5-4331-bc3c-76ff4a5ae4eb@linaro.org> (raw)
In-Reply-To: <9a8bf6f17a0f8b4e31a6d59c1adb735823f579aa.camel@linaro.org>
On 25/01/2024 15:10, André Draszik wrote:
>> [PATCH v2] arm64: dts: exynos: gs101: sysreg_peric0 needs a clock
>
> Sorry for copy/paste error in the subject :-(
>
> I've sent an update in https://lore.kernel.org/all/20240125140644.3617587-1-andre.draszik@linaro.org/
Which makes it impossible to apply (at least with usual workflow):
Grabbing thread from
lore.kernel.org/all/20240125140139.3616119-1-andre.draszik@linaro.org/t.mbox.gz
Checking for newer revisions
Grabbing search results from lore.kernel.org
Analyzing 4 messages in the thread
Will use the latest revision: v2
You can pick other revisions using the -vN flag
Checking attestation on all messages, may take a moment...
---
✓ [PATCH v2] arm64: dts: exynos: gs101: sysreg_peric0 needs a clock
+ Link:
https://lore.kernel.org/r/20240125140644.3617587-1-andre.draszik@linaro.org
+ Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
---
✓ Signed: DKIM/linaro.org
---
Total patches: 1
---
Applying: arm64: dts: exynos: gs101: sysreg_peric0 needs a clock
---
Patchwork: setting state on patchwork.kernel.org/linux-samsung-soc
-> under-review : [v2] arm64: dts: exynos: gs101: sysreg_peric0 needs a
clock
Please do not invent your own workflows of handling patches. Each
submission must be:
1. In separate thread, not linked to something else,
2. Complete.
I await for v3.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-01-26 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 14:01 [PATCH 1/2] dt-bindings: samsung: exynos-sysreg: gs101-peric0 requires a clock André Draszik
2024-01-25 14:01 ` [PATCH 2/2] arm64: dts: exynos: gs101: sysreg_peric1 needs " André Draszik
2024-01-25 14:06 ` [PATCH v2] arm64: dts: exynos: gs101: sysreg_peric0 " André Draszik
2024-01-25 14:10 ` [PATCH 2/2] arm64: dts: exynos: gs101: sysreg_peric1 " André Draszik
2024-01-26 10:35 ` Krzysztof Kozlowski [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=58ba835e-46d5-4331-bc3c-76ff4a5ae4eb@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.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;
as well as URLs for NNTP newsgroup(s).