From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Stafford Horne <shorne@gmail.com>,
Jonas Bonn <jonas@southpole.se>,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
linux-openrisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tools/nolibc: add support for OpenRISC / or1k
Date: Fri, 1 May 2026 09:59:14 +0200 [thread overview]
Message-ID: <afRdUjkM7aOFKpxQ@1wt.eu> (raw)
In-Reply-To: <5f223443-0136-4938-ac93-14876e788ff1@t-8ch.de>
On Wed, Apr 29, 2026 at 10:58:31PM +0200, Thomas Weißschuh wrote:
> On 2026-04-29 19:43:08+0100, Stafford Horne wrote:
> > On Wed, Apr 29, 2026 at 05:20:45PM +0200, Thomas Weißschuh wrote:
> > > Add support for OpenRISC / or1k to nolibc.
> > >
> > > _start() uses the same wrapper construct as in arch-sh.h.
> > > libgcc is necessary as OpenRISC is missing 64-bit multiplication.
> > >
> > > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> >
> > Acked-by: Stafford Horne <shorne@gmail.com>
>
> Thanks!
>
> > Do you want me to pick this up to send via the openrisc queue? Or do you prefer
> > it go via the selftests queue?
>
> I'll take it through the nolibc tree. Otherwise we'd get a bunch of
> merge conflicts, too.
>
> (...)
And from a nolibc perspective it's also an ack by me, thanks Thomas!
Acked-by: Willy Tarreau <w@1wt.eu>
willy
prev parent reply other threads:[~2026-05-01 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 15:20 [PATCH v2] tools/nolibc: add support for OpenRISC / or1k Thomas Weißschuh
2026-04-29 18:43 ` Stafford Horne
2026-04-29 20:58 ` Thomas Weißschuh
2026-05-01 7:59 ` Willy Tarreau [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=afRdUjkM7aOFKpxQ@1wt.eu \
--to=w@1wt.eu \
--cc=jonas@southpole.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=shorne@gmail.com \
--cc=stefan.kristiansson@saunalahti.fi \
/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