From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Jimmy Durand Wesolowski <jimmy.wesolowski@mobileye.com>
Cc: buildroot@buildroot.org, guenther.harrasser@mobileye.com,
Vladimir Kondratiev <vladimir.kondratiev@mobileye.com>
Subject: Re: [Buildroot] [PATCH] package/libunwind: enable on riscv 64-bit glibc
Date: Tue, 3 Feb 2026 08:54:28 +0100 [thread overview]
Message-ID: <aYGpdeovUesgfL1c@windsurf> (raw)
In-Reply-To: <20260202151908.1203336-1-jimmy.wesolowski@mobileye.com>
Hello,
Thanks for the patch, but Vladimir had already sent it, and it had
already been merged in Buildroot master. See more comments below
though.
On Mon, Feb 02, 2026 at 05:19:08PM +0200, Jimmy Durand Wesolowski via buildroot wrote:
> From: Vladimir Kondratiev <vladimir.kondratiev@mobileye.com>
>
> Since version 1.8, libunwind supports 64-bit riscv,
> at least with glibc
>
> Change-Id: Ia06dad0215baa34bef33f7693bd76ffb66f3a32a
The Change-Id shouldn't appear in Buildroot commits, as it's not
relevant for the Buildroot development process.
> Signed-off-by: Vladimir Kondratiev <vladimir.kondratiev@mobileye.com>
> (cherry picked from commit 180117f1ca693725f3b937341ac243a863f6746c)
This cherry picked message also doesn't make much sense in this
context.
> Signed-off-by: Jimmy Durand Wesolowski <jimmy.wesolowski@mobileye.com>
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-02-03 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 15:19 [Buildroot] [PATCH] package/libunwind: enable on riscv 64-bit glibc Jimmy Durand Wesolowski via buildroot
2026-02-03 7:54 ` Thomas Petazzoni via buildroot [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=aYGpdeovUesgfL1c@windsurf \
--to=buildroot@buildroot.org \
--cc=guenther.harrasser@mobileye.com \
--cc=jimmy.wesolowski@mobileye.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vladimir.kondratiev@mobileye.com \
/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