From: Qian Cai <quic_qiancai@quicinc.com>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] configs/debug: set CONFIG_DEBUG_INFO=y properly
Date: Tue, 8 Mar 2022 08:56:00 -0500 [thread overview]
Message-ID: <YidgcE0ypmKWzvai@qian> (raw)
In-Reply-To: <20220308104215.q4asb6z3vicq2vja@maple.lan>
On Tue, Mar 08, 2022 at 10:42:15AM +0000, Daniel Thompson wrote:
> On Tue, Mar 01, 2022 at 03:29:20PM -0500, Qian Cai wrote:
> > CONFIG_DEBUG_INFO can't be set by user directly,
>
> What do you mean by "can't be set by user directly"? DEBUG_INFO
> is fully controlable via menuconfig.
On linux-next, we no longer able to select DEBUG_INFO directly due to this
patch:
https://lore.kernel.org/all/20220125075126.891825-1-keescook@chromium.org/
Thus, this patch will work on both the mainline and linux-next.
> Does this change actually work in the kernels it has merged into?
>
> DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT existence is predicated on DEBUG_INFO
> being set. It makes no sense at all to set the former without the later.
It works fine here.
$ git reset --hard v5.17-rc7
$ rm .config
$ make ARCH=arm64 defconfig debug.config
$ grep -i debug_info .config
CONFIG_DEBUG_INFO=y
next prev parent reply other threads:[~2022-03-08 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 20:29 [PATCH] configs/debug: set CONFIG_DEBUG_INFO=y properly Qian Cai
2022-03-08 10:42 ` Daniel Thompson
2022-03-08 13:56 ` Qian Cai [this message]
2022-03-08 14:30 ` Daniel Thompson
2022-03-08 15:11 ` Qian Cai
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=YidgcE0ypmKWzvai@qian \
--to=quic_qiancai@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.thompson@linaro.org \
--cc=linux-kernel@vger.kernel.org \
/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.