From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 0/2] package/pixman: Fix riscv vector support
Date: Tue, 22 Apr 2025 21:41:03 +0200 [thread overview]
Message-ID: <20250422214103.149c90dd@windsurf> (raw)
In-Reply-To: <20250421-pixman_riscv_dependency-v2-0-7209dd6f2485@rivosinc.com>
Hello Charlie,
On Mon, 21 Apr 2025 14:37:02 -0700
Charlie Jenkins <charlie@rivosinc.com> wrote:
> Charlie Jenkins (2):
> package/pixman: Only compile with riscv vector support when selected
> package/pixman: Fix pixman compilation on riscv
Thanks, both applied.
Aside from the Upstream: link on the second patch, one thing that was
missing for the commit messages was since *when* the issue existed in
Buildroot, which helps the people who maintain our LTS/stable branches
to understand if those patches should be backported or not. So I've
added that information, but it would be great to include it in your
future contributions.
Thanks a lot!
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:[~2025-04-22 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 21:37 [Buildroot] [PATCH v2 0/2] package/pixman: Fix riscv vector support Charlie Jenkins
2025-04-21 21:37 ` [Buildroot] [PATCH v2 1/2] package/pixman: Only compile with riscv vector support when selected Charlie Jenkins
2025-04-21 21:37 ` [Buildroot] [PATCH v2 2/2] package/pixman: Fix pixman compilation on riscv Charlie Jenkins
2025-04-22 6:57 ` Thomas Petazzoni via buildroot
2025-04-22 17:54 ` Charlie Jenkins
2025-04-22 19:41 ` 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=20250422214103.149c90dd@windsurf \
--to=buildroot@buildroot.org \
--cc=charlie@rivosinc.com \
--cc=thomas.petazzoni@bootlin.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 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.