From: Michael Ellerman <mpe@ellerman.id.au>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-edac@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, tony.luck@intel.com
Subject: Re: [PATCH] EDAC/powerpc: Remove PPC_MAPLE drivers
Date: Tue, 19 Nov 2024 10:33:46 +1100 [thread overview]
Message-ID: <87a5dwi0bp.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20241118104142.GAZzsZ5vcY_Vv3GvY-@fat_crate.local>
Borislav Petkov <bp@alien8.de> writes:
> On Tue, Nov 12, 2024 at 07:41:34PM +1100, Michael Ellerman wrote:
>> These two drivers are only buildable for the powerpc "maple" platform
>> (CONFIG_PPC_MAPLE), which has now been removed, see
>> commit 62f8f307c80e ("powerpc/64: Remove maple platform").
>>
>> Remove the drivers.
>>
>> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
>> ---
>> drivers/edac/Kconfig | 18 --
>> drivers/edac/Makefile | 2 -
>> drivers/edac/amd8111_edac.c | 596 ------------------------------------
>> drivers/edac/amd8111_edac.h | 118 -------
>> drivers/edac/amd8131_edac.c | 358 ----------------------
>> drivers/edac/amd8131_edac.h | 107 -------
>> 6 files changed, 1199 deletions(-)
>> delete mode 100644 drivers/edac/amd8111_edac.c
>> delete mode 100644 drivers/edac/amd8111_edac.h
>> delete mode 100644 drivers/edac/amd8131_edac.c
>> delete mode 100644 drivers/edac/amd8131_edac.h
>>
>> The removal commit is in the powerpc/next branch:
>> https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/log/?h=next
>>
>> I can take this via the powerpc tree if that's easiest, let me know.
>
> Yes, please do.
Thanks, will do.
> I've been meaning to reply to you but then gazillion things interrupted me and
> ... you know how it is. Sorry.
No worries, I do know how it is :)
cheers
next prev parent reply other threads:[~2024-11-18 23:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 8:41 [PATCH] EDAC/powerpc: Remove PPC_MAPLE drivers Michael Ellerman
2024-11-18 10:41 ` Borislav Petkov
2024-11-18 23:33 ` Michael Ellerman [this message]
2024-11-25 9:48 ` 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=87a5dwi0bp.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).