linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: A <akira.2020@protonmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "tony.luck@intel.com" <tony.luck@intel.com>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: kernel 6.9-rc1 fails to compile if debugfs is disabled
Date: Mon, 25 Mar 2024 16:49:54 +0000	[thread overview]
Message-ID: <HCNla3hB7hRLtei6e9hDKTtNA8rpNlHjh6qeb6ysaiRniyNYBQFsbIqVPuHfIdOpkRAmL91XOFES7iumuKZcbUqZnOo59I6Sok1Irc3NcjU=@protonmail.com> (raw)
In-Reply-To: <20240325160818.GDZgGhcpLu3uks_K9z@fat_crate.local>






On Monday, March 25th, 2024 at 16:08, Borislav Petkov <bp@alien8.de> wrote:

> 
> 
> On Mon, Mar 25, 2024 at 03:10:25PM +0000, A wrote:
> 
> > https://bugzilla.kernel.org/show_bug.cgi?id=218640
> > 
> > kernel 6.9-rc1 fails to compile if debugfs is disabled (CONFIG_DEBUG_FS):
> 
> 
> This should fix it:
> 
> ---
> 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
> 
> 
> --
> Regards/Gruss,
> Boris.
> 
> https://people.kernel.org/tglx/notes-about-netiquette

thanks, this works

kind regards,
anthony s.k.

  reply	other threads:[~2024-03-25 16:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 15:10 kernel 6.9-rc1 fails to compile if debugfs is disabled A
2024-03-25 15:17 ` Fw: " A
2024-03-25 16:08 ` Borislav Petkov
2024-03-25 16:49   ` A [this message]
2024-03-25 17:38     ` Borislav Petkov

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='HCNla3hB7hRLtei6e9hDKTtNA8rpNlHjh6qeb6ysaiRniyNYBQFsbIqVPuHfIdOpkRAmL91XOFES7iumuKZcbUqZnOo59I6Sok1Irc3NcjU=@protonmail.com' \
    --to=akira.2020@protonmail.com \
    --cc=bp@alien8.de \
    --cc=linux-edac@vger.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 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).