From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>, Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Guillaume Tucker <guillaume.tucker@collabora.com>,
Kevin Hilman <khilman@baylibre.com>
Subject: Re: [PATCH v2] arm64: defconfig: Use DEBUG_INFO_REDUCED
Date: Mon, 15 Mar 2021 19:13:37 +0000 [thread overview]
Message-ID: <161583561181.30130.6744704793645913896.b4-ty@arm.com> (raw)
In-Reply-To: <20210304174407.17537-1-broonie@kernel.org>
On Thu, 4 Mar 2021 17:44:07 +0000, Mark Brown wrote:
> We've had DEBUG_INFO enabled for arm64 defconfigs since the initial
> commit. This is probably not that frequently used but substantially
> inflates the size of the build tree and amount of I/O needed during the
> build. This was causing issues with storage usage in some automated CI
> environments which don't expect defconfigs to be quite this big, and
> generally increases the resource consumption for both them and people
> doing local builds. The main use case for the debug info is decoding
> things with scripts/faddr2line but that doesn't need the full
> DEBUG_INFO, DEBUG_INFO_REDUCED is enough for it, so enable that by
> default.
>
> [...]
Applied to arm64 (for-next/misc), thanks!
[1/1] arm64: defconfig: Use DEBUG_INFO_REDUCED
https://git.kernel.org/arm64/c/ed938a4bfc58
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-03-15 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 17:44 [PATCH v2] arm64: defconfig: Use DEBUG_INFO_REDUCED Mark Brown
2021-03-04 18:30 ` Will Deacon
2021-03-04 18:33 ` Mark Brown
2021-03-04 18:49 ` Will Deacon
2021-03-15 19:13 ` Catalin Marinas [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=161583561181.30130.6744704793645913896.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=guillaume.tucker@collabora.com \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@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.