From: patchwork-bot+linux-soc@kernel.org
To: Doug Brown <doug@schmorgal.com>
Cc: soc@kernel.org
Subject: Re: [PATCH 0/2] ARM: mmp: PXA168 timer fixes
Date: Sun, 04 Dec 2022 12:20:15 +0000 [thread overview]
Message-ID: <167015641597.6046.760220284472846130.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221204005117.53452-1-doug@schmorgal.com>
Hello:
This series was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Sat, 3 Dec 2022 16:51:15 -0800 you wrote:
> This series contains a couple of bug fixes for the PXA168 timer. The
> clock wasn't assigned in pxa168.dtsi which eventually resulted in a hang
> at every boot after the clock was disabled. Also, the timer read
> function wasn't waiting long enough to capture the new timer value,
> which resulted in erroneous high CPU usage percent being reported with
> CONFIG_NO_HZ_IDLE=y.
>
> [...]
Here is the summary with links:
- [1/2] ARM: dts: pxa168: add timer reset and clock
https://git.kernel.org/soc/soc/c/7b3e7df92a06
- [2/2] ARM: mmp: fix timer_read delay
https://git.kernel.org/soc/soc/c/e348b4014c31
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-12-04 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 0:51 [PATCH 0/2] ARM: mmp: PXA168 timer fixes Doug Brown
2022-12-04 0:51 ` Doug Brown
2022-12-04 0:51 ` [PATCH 1/2] ARM: dts: pxa168: add timer reset and clock Doug Brown
2022-12-04 0:51 ` Doug Brown
2022-12-04 0:51 ` [PATCH 2/2] ARM: mmp: fix timer_read delay Doug Brown
2022-12-04 0:51 ` Doug Brown
2022-12-04 12:20 ` patchwork-bot+linux-soc [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=167015641597.6046.760220284472846130.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=doug@schmorgal.com \
--cc=soc@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 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.