public inbox for linux-edac@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: linux-edac <linux-edac@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"anthony s . k ." <akira.2020@protonmail.com>,
	Yazen Ghannam <yazen.ghannam@amd.com>
Subject: [PATCH] RAS/AMD/FMPM: Fix build when debugfs is not enabled
Date: Mon, 25 Mar 2024 19:37:55 +0100	[thread overview]
Message-ID: <20240325183755.776-1-bp@alien8.de> (raw)

From: "Borislav Petkov (AMD)" <bp@alien8.de>

Have the driver depend on DEBUG_FS as it is useless without it.

Fixes: 6f15e617cc99 ("RAS: Introduce a FRU memory poison manager")
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=218640
Reported-by: anthony s.k. <akira.2020@protonmail.com>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Cc: Yazen Ghannam <yazen.ghannam@amd.com>
---
 drivers/ras/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/ras/Kconfig b/drivers/ras/Kconfig
index fc4f4bb94a4c..41697e326fa6 100644
--- a/drivers/ras/Kconfig
+++ b/drivers/ras/Kconfig
@@ -37,7 +37,7 @@ source "drivers/ras/amd/atl/Kconfig"
 config RAS_FMPM
 	tristate "FRU Memory Poison Manager"
 	default m
-	depends on AMD_ATL && ACPI_APEI
+	depends on AMD_ATL && ACPI_APEI && DEBUG_FS
 	help
 	  Support saving and restoring memory error information across reboot
 	  using ACPI ERST as persistent storage. Error information is saved with
-- 
2.43.0


             reply	other threads:[~2024-03-25 18:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 18:37 Borislav Petkov [this message]
2024-03-26 13:41 ` [PATCH] RAS/AMD/FMPM: Fix build when debugfs is not enabled Yazen Ghannam
2024-03-26 14:07   ` Borislav Petkov
2024-03-26 14:22     ` Yazen Ghannam
2024-03-26 14:27       ` Borislav Petkov
2024-03-26 14:20   ` A
2024-03-26 14:29     ` Yazen Ghannam
2024-03-26 18:37       ` A

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=20240325183755.776-1-bp@alien8.de \
    --to=bp@alien8.de \
    --cc=akira.2020@protonmail.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yazen.ghannam@amd.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