From: Andrew Morton <akpm@linux-foundation.org>
To: Will Deacon <will@kernel.org>
Cc: Yicong Yang <yangyicong@huawei.com>,
catalin.marinas@arm.com, dianders@chromium.org,
sumit.garg@linaro.org, kernelfans@gmail.com,
lecopzer.chen@mediatek.com, tglx@linutronix.de, song@kernel.org,
linux-arm-kernel@lists.infradead.org,
jonathan.cameron@huawei.com, zhanjie9@hisilicon.com,
prime.zeng@hisilicon.com, yangyicong@hisilicon.com,
linuxarm@huawei.com
Subject: Re: [PATCH v2 0/2] Update the watchdog period according to real CPU frequency
Date: Fri, 27 Jun 2025 11:56:56 -0700 [thread overview]
Message-ID: <20250627115656.824d10b741f6b6cbaa629ea4@linux-foundation.org> (raw)
In-Reply-To: <aF64F2cW3aratui5@willie-the-truck>
On Fri, 27 Jun 2025 16:26:15 +0100 Will Deacon <will@kernel.org> wrote:
> > Can I assume that the ARM maintainers will be handling this?
>
> Argh, this has all ended up in my spam for some reason...
So you won't be buying these ED meds?
> Lemme go fish the patches back out. Andrew -- we can take these via
> arm64 if you like (although I have some comments on the code first).
No probs, I dropped the mm.git copy.
prev parent reply other threads:[~2025-06-27 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 13:09 [PATCH v2 0/2] Update the watchdog period according to real CPU frequency Yicong Yang
2025-05-12 13:09 ` [PATCH v2 1/2] watchdog/perf: Provide function for adjusting the event period Yicong Yang
2025-05-12 23:07 ` Andrew Morton
2025-05-13 7:02 ` Yicong Yang
2025-05-12 13:09 ` [PATCH v2 2/2] arm64/watchdog_hld: Add a cpufreq notifier for update watchdog thresh Yicong Yang
2025-05-12 23:06 ` [PATCH v2 0/2] Update the watchdog period according to real CPU frequency Andrew Morton
2025-05-13 6:51 ` Yicong Yang
2025-06-27 15:26 ` Will Deacon
2025-06-27 18:56 ` Andrew Morton [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=20250627115656.824d10b741f6b6cbaa629ea4@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dianders@chromium.org \
--cc=jonathan.cameron@huawei.com \
--cc=kernelfans@gmail.com \
--cc=lecopzer.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=prime.zeng@hisilicon.com \
--cc=song@kernel.org \
--cc=sumit.garg@linaro.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.com \
--cc=yangyicong@huawei.com \
--cc=zhanjie9@hisilicon.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