From: patchwork-bot+linux-amlogic@kernel.org
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, khilman@kernel.org
Subject: Re: [PATCH 0/2] arm64: dts: meson-sm1: add thermal nodes
Date: Wed, 20 May 2020 00:01:29 +0000 [thread overview]
Message-ID: <158993288940.29142.8049006002077258199.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20200512093916.19676-1-narmstrong@baylibre.com>
Hello:
This series was applied to khilman/linux-amlogic.git (refs/heads/for-next).
On Tue, 12 May 2020 11:39:14 +0200 you wrote:
> SM1 Thermal is missing and broken since the G12A/G12B thermal enablement,
> fix this here by moving the g12b thermal nodes to meson-g12b.dtsi
> and adding the proper sm1 thermal nodes.
>
> Neil Armstrong (2):
> arm64: dts: meson-g12b: move G12B thermal nodes to meson-g12b.dtsi
> arm64: dts: meson-sm1: add cpu thermal nodes
>
> [...]
Here is a summary with links:
- [1/2] arm64: dts: meson-g12b: move G12B thermal nodes to meson-g12b.dtsi
https://git.kernel.org/khilman/linux-amlogic/c/fc9eab4b4276481ab1625d56bde57a87d73987bb
- [2/2] arm64: dts: meson-sm1: add cpu thermal nodes
https://git.kernel.org/khilman/linux-amlogic/c/c30dd9270197d060dae9e6d8f0b7f7864341cb2c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/pwbot
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2020-05-20 0:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 9:39 [PATCH 0/2] arm64: dts: meson-sm1: add thermal nodes Neil Armstrong
2020-05-12 9:39 ` [PATCH 1/2] arm64: dts: meson-g12b: move G12B thermal nodes to meson-g12b.dtsi Neil Armstrong
2020-05-12 9:39 ` [PATCH 2/2] arm64: dts: meson-sm1: add cpu thermal nodes Neil Armstrong
2020-05-19 23:10 ` [PATCH 0/2] arm64: dts: meson-sm1: add " Kevin Hilman
2020-05-20 0:01 ` patchwork-bot+linux-amlogic [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=158993288940.29142.8049006002077258199.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-amlogic@kernel.org \
--cc=khilman@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=narmstrong@baylibre.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).