From: Willy Tarreau <w@1wt.eu>
To: Zhangjin Wu <falcon@tinylab.org>
Cc: thomas@t-8ch.de, arnd@arndb.de, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux@weissschuh.net
Subject: Re: [PATCH v4 08/12] selftests/nolibc: add test support for ppc
Date: Wed, 2 Aug 2023 09:48:42 +0200 [thread overview]
Message-ID: <ZMoKWheH5mrCXogy@1wt.eu> (raw)
In-Reply-To: <20230802052150.138283-1-falcon@tinylab.org>
Hi Zhangjin,
On Wed, Aug 02, 2023 at 01:21:50PM +0800, Zhangjin Wu wrote:
> Hi, Willy, Thomas
>
> Yuan is helping me to test this series and the tinyconfig series with
> the latest compilers.
>
> His first test found this ppc support failed with stackprotector when
> using a newer compiler (I used an older compiler without stackprotector
> for ppc), I'm debugging it, so, please ignore this revision too, of
> course, if time allows, welcome to take a look at the other patches.
>
> His other tests are trying to find out the exact poweroff support
> options for every architecture one by one, let's fill this gap ...
Thanks for notifying us. I strongly suggest that you leave ppc32 aside
for now, until the rest is completely validated and merged. It turns
out that your willingness to work around some of the oddities met on
this one have resulted in a lot of drift away from the "keep it simple"
principle and significantly delayed the possibilities to integrate the
rest of your work. It would be much saner to only focus on ppc64/ppc64le
and figure later how to make ppc32 work (or decide not to support it if
it's not worth the effort in the end).
Regards,
willy
next prev parent reply other threads:[~2023-08-02 7:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 19:36 [PATCH v4 00/12] tools/nolibc: add 32/64-bit powerpc support Zhangjin Wu
2023-08-01 19:37 ` [PATCH v4 01/12] tools/nolibc: add support for powerpc Zhangjin Wu
2023-08-01 19:38 ` [PATCH v4 02/12] tools/nolibc: add support for powerpc64 Zhangjin Wu
2023-08-01 19:39 ` [PATCH v4 03/12] selftests/nolibc: fix up O= option support Zhangjin Wu
2023-08-01 19:40 ` [PATCH v4 04/12] selftests/nolibc: add macros to reduce duplicated changes Zhangjin Wu
2023-08-01 19:41 ` [PATCH v4 05/12] selftests/nolibc: add XARCH and ARCH mapping support Zhangjin Wu
2023-08-01 19:42 ` [PATCH v4 06/12] selftests/nolibc: add nolibc-test-config target Zhangjin Wu
2023-08-01 19:43 ` [PATCH v4 07/12] selftests/nolibc: add help for " Zhangjin Wu
2023-08-01 19:44 ` [PATCH v4 08/12] selftests/nolibc: add test support for ppc Zhangjin Wu
2023-08-02 5:21 ` Zhangjin Wu
2023-08-02 7:48 ` Willy Tarreau [this message]
2023-08-02 10:32 ` Zhangjin Wu
2023-08-02 16:03 ` Zhangjin Wu
2023-08-02 21:36 ` Thomas Weißschuh
2023-08-03 2:05 ` Willy Tarreau
2023-08-03 2:58 ` Zhangjin Wu
2023-08-03 4:37 ` Willy Tarreau
2023-08-03 7:51 ` Zhangjin Wu
2023-08-01 19:45 ` [PATCH v4 09/12] selftests/nolibc: add test support for ppc64le Zhangjin Wu
2023-08-01 19:46 ` [PATCH v4 10/12] selftests/nolibc: add test support for ppc64 Zhangjin Wu
2023-08-01 19:47 ` [PATCH v4 11/12] selftests/nolibc: allow customize CROSS_COMPILE by architecture Zhangjin Wu
2023-08-01 19:49 ` [PATCH v4 12/12] selftests/nolibc: customize CROSS_COMPILE for 32/64-bit powerpc Zhangjin Wu
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=ZMoKWheH5mrCXogy@1wt.eu \
--to=w@1wt.eu \
--cc=arnd@arndb.de \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=thomas@t-8ch.de \
/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