From: Borislav Petkov <bp@alien8.de>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: mchehab@kernel.org, tony.luck@intel.com, james.morse@arm.com,
rric@kernel.org, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] EDAC/mv64x60: Remove orphan mv64x60 driver
Date: Mon, 7 Dec 2020 12:17:27 +0100 [thread overview]
Message-ID: <20201207111727.GC20489@zn.tnic> (raw)
In-Reply-To: <20201207040253.628528-1-mpe@ellerman.id.au>
On Mon, Dec 07, 2020 at 03:02:53PM +1100, Michael Ellerman wrote:
> The mv64x60 EDAC driver depends on CONFIG_MV64X60. But that symbol is
> not user-selectable, and the last code that selected it was removed
> with the C2K board support in 2018, see:
>
> 92c8c16f3457 ("powerpc/embedded6xx: Remove C2K board support")
>
> That means the driver is now dead code, so remove it.
>
> Suggested-by: Borislav Petkov <bp@alien8.de>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> ---
> drivers/edac/Kconfig | 7 -
> drivers/edac/Makefile | 1 -
> drivers/edac/mv64x60_edac.c | 883 ------------------------------------
> drivers/edac/mv64x60_edac.h | 114 -----
> 4 files changed, 1005 deletions(-)
> delete mode 100644 drivers/edac/mv64x60_edac.c
> delete mode 100644 drivers/edac/mv64x60_edac.h
Gladly taken and applied, thanks!
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: tony.luck@intel.com, rric@kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
james.morse@arm.com, mchehab@kernel.org,
linux-edac@vger.kernel.org
Subject: Re: [PATCH] EDAC/mv64x60: Remove orphan mv64x60 driver
Date: Mon, 7 Dec 2020 12:17:27 +0100 [thread overview]
Message-ID: <20201207111727.GC20489@zn.tnic> (raw)
In-Reply-To: <20201207040253.628528-1-mpe@ellerman.id.au>
On Mon, Dec 07, 2020 at 03:02:53PM +1100, Michael Ellerman wrote:
> The mv64x60 EDAC driver depends on CONFIG_MV64X60. But that symbol is
> not user-selectable, and the last code that selected it was removed
> with the C2K board support in 2018, see:
>
> 92c8c16f3457 ("powerpc/embedded6xx: Remove C2K board support")
>
> That means the driver is now dead code, so remove it.
>
> Suggested-by: Borislav Petkov <bp@alien8.de>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> ---
> drivers/edac/Kconfig | 7 -
> drivers/edac/Makefile | 1 -
> drivers/edac/mv64x60_edac.c | 883 ------------------------------------
> drivers/edac/mv64x60_edac.h | 114 -----
> 4 files changed, 1005 deletions(-)
> delete mode 100644 drivers/edac/mv64x60_edac.c
> delete mode 100644 drivers/edac/mv64x60_edac.h
Gladly taken and applied, thanks!
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-12-07 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 4:02 [PATCH] EDAC/mv64x60: Remove orphan mv64x60 driver Michael Ellerman
2020-12-07 4:02 ` Michael Ellerman
2020-12-07 11:17 ` Borislav Petkov [this message]
2020-12-07 11:17 ` Borislav Petkov
2020-12-08 9:02 ` Michael Ellerman
2020-12-08 9:02 ` Michael Ellerman
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=20201207111727.GC20489@zn.tnic \
--to=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mchehab@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=rric@kernel.org \
--cc=tony.luck@intel.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 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.