From: Peter Zijlstra <peterz@infradead.org>
To: Dmitrii Bundin <dmitrii.bundin.a@gmail.com>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Dan Williams <dan.j.williams@intel.com>,
Eric Dumazet <edumazet@google.com>,
Isabella Basso <isabbasso@riseup.net>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Kees Cook <keescook@chromium.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Fangrui Song <maskray@google.com>,
Michal Marek <michal.lkml@markovi.net>,
Nathan Chancellor <nathan@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH v3] kbuild: add debug level and macro defs options
Date: Tue, 23 Aug 2022 08:06:15 +0200 [thread overview]
Message-ID: <YwRuVywxTxPiIKbM@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <CANXV_Xw2wzwDdJkyV1nHPQm2JTt48SLrNc7YwrfcxOwuFA-z3w@mail.gmail.com>
On Sat, Aug 20, 2022 at 01:52:04AM +0300, Dmitrii Bundin wrote:
> On Fri, Aug 19, 2022 at 8:42 PM Nick Desaulniers
> <ndesaulniers@google.com> wrote:
> >
> > Is any of this really necessary?
>
> Consider the case if CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT=y.
Can I just say I *HATE* that thing? It uesd to be I could do:
../scripts/config --enable DEBUG_INFO
and I'd get a debug-info build, now I gotta use that horrible piece of
crap you just mentioned which I mis-type at least once every single
time.
prev parent reply other threads:[~2022-08-23 6:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 0:20 [PATCH v2] kbuild: add configurable debug info level Dmitrii Bundin
2022-08-14 2:01 ` Masahiro Yamada
2022-08-14 5:31 ` Fangrui Song
2022-08-14 18:58 ` Masahiro Yamada
2022-08-14 19:17 ` Dmitrii Bundin
2022-08-15 1:33 ` [PATCH v3] kbuild: add debug level and macro defs options Dmitrii Bundin
2022-08-18 4:13 ` Masahiro Yamada
2022-08-18 18:57 ` Dmitrii Bundin
2022-08-19 17:42 ` Nick Desaulniers
2022-08-19 22:52 ` Dmitrii Bundin
2022-08-22 16:45 ` Nick Desaulniers
2022-08-22 21:36 ` Nick Desaulniers
2022-08-22 22:42 ` Dmitrii Bundin
2022-08-24 23:25 ` Nick Desaulniers
2022-09-29 21:06 ` Masahiro Yamada
2022-09-30 9:11 ` Masahiro Yamada
2022-10-08 7:24 ` Dmitrii Bundin
2022-08-23 6:06 ` Peter Zijlstra [this message]
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=YwRuVywxTxPiIKbM@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dmitrii.bundin.a@gmail.com \
--cc=edumazet@google.com \
--cc=isabbasso@riseup.net \
--cc=jpoimboe@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=masahiroy@kernel.org \
--cc=maskray@google.com \
--cc=michal.lkml@markovi.net \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=vbabka@suse.cz \
/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