From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Keguang Zhang <keguang.zhang@gmail.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-mips@vger.kernel.org,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH v2 1/3] MIPS: Loongson32: Remove deprecated PWM timer clocksource
Date: Thu, 30 Mar 2023 13:30:03 +0200 [thread overview]
Message-ID: <20230330113003.GA9674@alpha.franken.de> (raw)
In-Reply-To: <20230330101506.545040-2-keguang.zhang@gmail.com>
On Thu, Mar 30, 2023 at 06:15:04PM +0800, Keguang Zhang wrote:
> The Loongson1 PWM timer will be moved to clocksource framework.
> Then, the old driver is no longer needed.
> Remove the deprecated code and update the Kconfig.
>
> Signed-off-by: Keguang Zhang <keguang.zhang@gmail.com>
> ---
> V1 -> V2: Delete the obsolete header file regs-pwm.h
> ---
> .../include/asm/mach-loongson32/regs-pwm.h | 25 ---
> arch/mips/loongson32/Kconfig | 37 ---
> arch/mips/loongson32/common/time.c | 210 ------------------
> 3 files changed, 272 deletions(-)
> delete mode 100644 arch/mips/include/asm/mach-loongson32/regs-pwm.h
Acked-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2023-03-30 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 10:15 [PATCH v2 0/3] Move Loongson1 PWM timer to clocksource framework Keguang Zhang
2023-03-30 10:15 ` [PATCH v2 1/3] MIPS: Loongson32: Remove deprecated PWM timer clocksource Keguang Zhang
2023-03-30 11:30 ` Thomas Bogendoerfer [this message]
2023-03-30 10:15 ` [PATCH v2 2/3] dt-bindings: timer: Add Loongson-1 clocksource Keguang Zhang
2023-03-30 10:15 ` [PATCH v2 3/3] clocksource: loongson1: Move PWM timer to clocksource framework Keguang Zhang
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=20230330113003.GA9674@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=keguang.zhang@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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