All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: Daniel Latypov <dlatypov@google.com>
Cc: brendanhiggins@google.com, davidgow@google.com,
	keescook@chromium.org, linux-kernel@vger.kernel.org,
	kunit-dev@googlegroups.com, linux-kselftest@vger.kernel.org,
	skhan@linuxfoundation.org
Subject: Re: [PATCH] Documentation: kunit: update kconfig options needed for UML coverage
Date: Mon, 28 Mar 2022 09:58:12 +0200	[thread overview]
Message-ID: <20220328075812.edzufjsxzzwbetlt@houat> (raw)
In-Reply-To: <20220326003356.487828-1-dlatypov@google.com>

[-- Attachment #1: Type: text/plain, Size: 532 bytes --]

On Fri, Mar 25, 2022 at 05:33:56PM -0700, Daniel Latypov wrote:
> Recent changes have made it so the current set is not sufficient.
> Namely, CONFIG_DEBUG_INFO is not being set even when explicitly asked.
> 
> Specifying a version of the debug info fixes this.
> Pick CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT as an option that's
> hopefully less fragile (esp. given we're tied to GCC 6 and lower).
> 
> Signed-off-by: Daniel Latypov <dlatypov@google.com>

Tested-by: Maxime Ripard <maxime@cerno.tech>

Thanks!
Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2022-03-28  7:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-26  0:33 [PATCH] Documentation: kunit: update kconfig options needed for UML coverage Daniel Latypov
2022-03-26  2:56 ` David Gow
2022-03-28 16:35   ` Daniel Latypov
2022-03-28 16:54     ` Brendan Higgins
2022-03-28 18:58       ` Daniel Latypov
2022-03-28 19:36         ` Brendan Higgins
2022-03-28  7:58 ` Maxime Ripard [this message]
2022-03-28 16:27 ` Brendan Higgins

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=20220328075812.edzufjsxzzwbetlt@houat \
    --to=maxime@cerno.tech \
    --cc=brendanhiggins@google.com \
    --cc=davidgow@google.com \
    --cc=dlatypov@google.com \
    --cc=keescook@chromium.org \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=skhan@linuxfoundation.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.