Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Luis Henriques <luis@igalia.com>
Cc: "Achill Gilgenast" <fossdd@pwned.life>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	<linux-kselftest@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<stable@vger.kernel.org>
Subject: Re: [RESEND PATCH v2] kallsyms: fix build without execinfo
Date: Tue, 1 Jul 2025 12:09:20 -0700	[thread overview]
Message-ID: <20250701120920.49cd122526b3032a4db1e218@linux-foundation.org> (raw)
In-Reply-To: <87ecuz51eg.fsf@igalia.com>

On Tue, 01 Jul 2025 17:19:51 +0100 Luis Henriques <luis@igalia.com> wrote:

> >> No, since backtrace_symbols is provided by execinfo.h.
> >
> > Is there some status on it? I saw you picked it in mm-hotfixes-unstable,
> > but it got dropped out again.
> >
> > Is there something I can do to push it?
> 
> FWIW I can confirm this is indeed a regression.  And specially annoying
> because it has been backported into stable kernels (even if having kunit
> tests backported sounds odd to me).
> 
> It would be great to have this fixed, or reverted.

OK, thanks for the reminder, I restored this.

      reply	other threads:[~2025-07-01 19:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-22  1:45 [RESEND PATCH v2] kallsyms: fix build without execinfo Achill Gilgenast
2025-06-22 18:36 ` Andrew Morton
2025-06-23 11:53   ` Achill Gilgenast
2025-07-01 11:37     ` Achill Gilgenast
2025-07-01 16:19       ` Luis Henriques
2025-07-01 19:09         ` Andrew Morton [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=20250701120920.49cd122526b3032a4db1e218@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=fossdd@pwned.life \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=luis@igalia.com \
    --cc=skhan@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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