From: David Vernet <void@manifault.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH sched_ext/for-6.12] sched_ext: Build fix on !CONFIG_STACKTRACE[_SUPPORT]
Date: Wed, 31 Jul 2024 14:06:54 -0500 [thread overview]
Message-ID: <20240731190654.GA6429@maniforge> (raw)
In-Reply-To: <ZqqI349WxdejfXZM@slm.duckdns.org>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
On Wed, Jul 31, 2024 at 08:56:31AM -1000, Tejun Heo wrote:
> scx_dump_task() uses stack_trace_save_tsk() which is only available when
> CONFIG_STACKTRACE. Make CONFIG_SCHED_CLASS_EXT select CONFIG_STACKTRACE if
> the support is available and skip capturing stack trace if
> !CONFIG_STACKTRACE.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202407161844.reewQQrR-lkp@intel.com/
Acked-by: David Vernet <void@manifault.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-07-31 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 18:56 [PATCH sched_ext/for-6.12] sched_ext: Build fix on !CONFIG_STACKTRACE[_SUPPORT] Tejun Heo
2024-07-31 19:06 ` David Vernet [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=20240731190654.GA6429@maniforge \
--to=void@manifault.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox