From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dmitry Chestnykh <dm.chestnykh@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 3/3] configs/qemu_sparc_ss10_defconfig: Re-introduce.
Date: Mon, 6 May 2024 22:40:54 +0200 [thread overview]
Message-ID: <20240506224054.218238be@windsurf> (raw)
In-Reply-To: <20240502045518.4875-3-dm.chestnykh@gmail.com>
Hello,
On Thu, 2 May 2024 07:55:18 +0300
Dmitry Chestnykh <dm.chestnykh@gmail.com> wrote:
> With uClibc-ng-1.0.48 we can restore this config
> because uClibc-ng was provided the fix for SPARC.
>
> Signed-off-by: Dmitry Chestnykh <dm.chestnykh@gmail.com>
Could you confirm that the instructions in
board/qemu/sparc-ss10/readme.txt are still valid?
Also, could you in this same commit add yourself in the DEVELOPERS file
for this defconfig and the board/qemu/sparc-ss10/ ?
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
next prev parent reply other threads:[~2024-05-06 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 4:55 [Buildroot] [PATCH v2 1/3] package/uclibc: Bump to 1.0.48 Dmitry Chestnykh
2024-05-02 4:55 ` [Buildroot] [PATCH v2 2/3] arch/Config.in: Allow building buildroot toolchain Dmitry Chestnykh
2024-05-06 20:39 ` Thomas Petazzoni via buildroot
2024-05-02 4:55 ` [Buildroot] [PATCH v2 3/3] configs/qemu_sparc_ss10_defconfig: Re-introduce Dmitry Chestnykh
2024-05-06 20:40 ` Thomas Petazzoni via buildroot [this message]
2024-05-06 20:39 ` [Buildroot] [PATCH v2 1/3] package/uclibc: Bump to 1.0.48 Thomas Petazzoni via buildroot
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=20240506224054.218238be@windsurf \
--to=buildroot@buildroot.org \
--cc=dm.chestnykh@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