From: Michael Ellerman <mpe@ellerman.id.au>
To: Guenter Roeck <linux@roeck-us.net>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-watchdog@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] watchdog: Remove MV64x60 watchdog driver
Date: Mon, 17 May 2021 21:17:13 +1000 [thread overview]
Message-ID: <87im3hk3t2.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <31d702e5-22d1-1766-76dd-e24860e5b1a4@roeck-us.net>
Guenter Roeck <linux@roeck-us.net> writes:
> On 3/18/21 10:25 AM, Christophe Leroy wrote:
>> Commit 92c8c16f3457 ("powerpc/embedded6xx: Remove C2K board support")
>> removed the last selector of CONFIG_MV64X60.
>>
>> Therefore CONFIG_MV64X60_WDT cannot be selected anymore and
>> can be removed.
>>
>> Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
>
> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
>
>> ---
>> drivers/watchdog/Kconfig | 4 -
>> drivers/watchdog/Makefile | 1 -
>> drivers/watchdog/mv64x60_wdt.c | 324 ---------------------------------
>> include/linux/mv643xx.h | 8 -
>> 4 files changed, 337 deletions(-)
>> delete mode 100644 drivers/watchdog/mv64x60_wdt.c
I assumed this would go via the watchdog tree, but seems like I
misinterpreted.
Should I take this via the powerpc tree for v5.14 ?
cheers
next prev parent reply other threads:[~2021-05-17 11:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 17:25 [PATCH] watchdog: Remove MV64x60 watchdog driver Christophe Leroy
2021-03-18 17:25 ` [PATCH] powerpc/embedded6xx: Remove CONFIG_MV64X60 Christophe Leroy
2021-03-18 19:22 ` Wolfram Sang
2021-03-31 1:09 ` Michael Ellerman
2021-03-18 17:25 ` [PATCH] net: marvell: Remove reference to CONFIG_MV64X60 Christophe Leroy
2021-03-18 21:30 ` patchwork-bot+netdevbpf
2021-03-18 18:32 ` [PATCH] watchdog: Remove MV64x60 watchdog driver Guenter Roeck
2021-05-17 11:17 ` Michael Ellerman [this message]
2021-05-17 13:39 ` Guenter Roeck
2021-06-07 1:43 ` Michael Ellerman
2021-06-07 11:29 ` Guenter Roeck
2021-06-20 13:30 ` gituser
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=87im3hk3t2.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=wim@linux-watchdog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox