Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: buildroot@buildroot.org,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Romain Naour <romain.naour@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Dick Olsson <hi@senzilla.io>
Subject: Re: [Buildroot] [PATCH v3 02/11] arch: Introduce LoongArch64
Date: Sat, 05 Jul 2025 19:50:42 +0200	[thread overview]
Message-ID: <ecc1d845fa77dc51dc67bf25fe08de42@free.fr> (raw)
In-Reply-To: <dbf55473-aede-485c-a896-8d014d103d06@app.fastmail.com>

Hi Jiaxun,

On 05/07/2025 15:24, Jiaxun Yang wrote:
> 在2025年7月5日周六 下午1:17,Julien Olivain写道:
>> Hi Jiaxun,
>> 
> Hi Julien,
> 
> All sounds good to me! Many thanks for looking into it.
> 
> [...]
> 
>> If you promise to help us doing this maintenance, I think we could
>> this series merged soon.
> 
> Sure, I will try my best.
> 
> I just want to note that I'm a hobbyist so my availability may vary,
> but it should be fine to devote a couple of hours per week.
> 
> I'll monitor Cc from buildroot list promptly.

Thanks for your confirmation.

With that, I just merged this series into master.

Let's see how it goes with the autobuilders.

>> 
>> What do you think?
> 
> Thanks again.
> 
>> 
>> Best regards,
>> 
>> Julien.
> 
> --
> - Jiaxun

Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-07-05 17:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18 18:20 [Buildroot] [PATCH v3 00/11] LoongArch64 initial support Jiaxun Yang
2025-06-18 18:20 ` [Buildroot] [PATCH v3 01/11] package/gcc: Introduce BR2_GCC_TARGET_SIMD option Jiaxun Yang
2025-06-18 18:20 ` [Buildroot] [PATCH v3 02/11] arch: Introduce LoongArch64 Jiaxun Yang
2025-07-05 12:17   ` Julien Olivain via buildroot
2025-07-05 13:24     ` Jiaxun Yang
2025-07-05 17:50       ` Julien Olivain via buildroot [this message]
2025-07-05 18:14         ` Jiaxun Yang
2025-07-05 19:46           ` Julien Olivain via buildroot
2025-06-18 18:20 ` [Buildroot] [PATCH v3 03/11] package/glibc: Enable LoongArch64 support Jiaxun Yang
2025-06-18 18:20 ` [Buildroot] [PATCH v3 04/11] package/musl: " Jiaxun Yang
2025-06-18 18:20 ` [Buildroot] [PATCH v3 05/11] linux: Introduce {vmlinux, vmlinuz}.efi kernel binary format Jiaxun Yang
2025-06-18 18:20 ` [Buildroot] [PATCH v3 06/11] boot/grub2: Introduce loongarch64-efi target Jiaxun Yang
2025-06-18 18:20 ` [Buildroot] [PATCH v3 07/11] configs/loongarch64_efi: new defconfig Jiaxun Yang
2025-06-18 18:20 ` [Buildroot] [PATCH v3 08/11] boot/edk2: Add LoongArch64 OVMF support Jiaxun Yang
2025-06-18 18:20 ` [Buildroot] [PATCH v3 09/11] package/qemu: enable loongarch64 as target package Jiaxun Yang
2025-06-18 18:20 ` [Buildroot] [PATCH v3 10/11] configs/qemu_loongarch64_virt_efi: new defconfig Jiaxun Yang
2025-06-18 18:20 ` [Buildroot] [PATCH v3 11/11] support/config-fragments: Add LoongArch64 toolchain support Jiaxun Yang

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=ecc1d845fa77dc51dc67bf25fe08de42@free.fr \
    --to=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=hi@senzilla.io \
    --cc=jiaxun.yang@flygoat.com \
    --cc=ju.o@free.fr \
    --cc=romain.naour@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox