From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: shmobile: defconfig: Restore debugfs support
Date: Tue, 10 Dec 2019 18:09:37 +0100 [thread overview]
Message-ID: <20191210170937.GA6956@bigcity.dyn.berto.se> (raw)
In-Reply-To: <20191209101327.26571-1-geert+renesas@glider.be>
Hi Geert,
Thanks for your patch.
On 2019-12-09 11:13:27 +0100, Geert Uytterhoeven wrote:
> Since commit 0e4a459f56c32d3e ("tracing: Remove unnecessary DEBUG_FS
> dependency"), CONFIG_DEBUG_FS is no longer auto-enabled. This breaks
> booting Debian 9, as systemd needs debugfs:
>
> [FAILED] Failed to mount /sys/kernel/debug.
> See 'systemctl status sys-kernel-debug.mount' for details.
> [DEPEND] Dependency failed for Local File Systems.
> ...
> You are in emergGive root password for maintenance
> (or press Control-D to continue):
>
> Fix this by enabling CONFIG_DEBUG_FS explicitly.
>
> See also commit 18977008f44c66bd ("ARM: multi_v7_defconfig: Restore
> debugfs support").
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> ---
> To be queued as a fix for v5.5.
> ---
> arch/arm/configs/shmobile_defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
> index 7f0985e023313b57..64fa849f8bbe0617 100644
> --- a/arch/arm/configs/shmobile_defconfig
> +++ b/arch/arm/configs/shmobile_defconfig
> @@ -215,4 +215,5 @@ CONFIG_DMA_CMA=y
> CONFIG_CMA_SIZE_MBYTES=64
> CONFIG_PRINTK_TIME=y
> # CONFIG_ENABLE_MUST_CHECK is not set
> +CONFIG_DEBUG_FS=y
> CONFIG_DEBUG_KERNEL=y
> --
> 2.17.1
>
--
Regards,
Niklas Söderlund
next prev parent reply other threads:[~2019-12-10 17:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 10:05 [PATCH] soc: renesas: Remove ARCH_R8A7796 Geert Uytterhoeven
2019-12-11 13:13 ` [PATCH/RFC] arm64: dts: renesas: Rename r8a7796* to r8a77960* Geert Uytterhoeven
2019-12-11 10:04 ` [PATCH] arm64: dts: renesas: Remove use of ARCH_R8A7796 Geert Uytterhoeven
2019-12-09 10:13 ` [PATCH] ARM: shmobile: defconfig: Restore debugfs support Geert Uytterhoeven
2019-12-09 10:14 ` [PATCH] [LOCAL] arm64: renesas_defconfig: Refresh for v5.5-rc1 Geert Uytterhoeven
2019-12-09 10:36 ` Patchwork summary for: linux-renesas-soc patchwork-bot+linux-renesas-soc
2019-12-09 13:23 ` Geert Uytterhoeven
2019-12-11 10:06 ` [PATCH LOCAL] arm64: defconfig: Enable CONFIG_ARCH_R8A77960 Geert Uytterhoeven
2019-12-13 21:40 ` Patchwork summary for: linux-renesas-soc patchwork-bot+linux-renesas-soc
2019-12-10 17:09 ` Niklas Söderlund [this message]
2019-12-13 21:40 ` patchwork-bot+linux-renesas-soc
2019-12-11 17:55 ` [PATCH/RFC] arm64: dts: renesas: Rename r8a7796* to r8a77960* Laurent Pinchart
2019-12-11 19:52 ` Eugeniu Rosca
2019-12-12 9:11 ` Geert Uytterhoeven
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=20191210170937.GA6956@bigcity.dyn.berto.se \
--to=niklas.soderlund@ragnatech.se \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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).