From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Willy Tarreau <w@1wt.eu>
Cc: Brian Cain <bcain@kernel.org>, Shuah Khan <shuah@kernel.org>,
linux-hexagon@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 3/3] tools/nolibc: add support for hexagon
Date: Wed, 19 Aug 2026 20:29:42 +0200 [thread overview]
Message-ID: <55da1de0-b034-4b3a-8b25-e4cedfeb4418@t-8ch.de> (raw)
In-Reply-To: <aoVXbwcC1qToZTr-@1wt.eu>
On 2026-08-19 09:12:47+0200, Willy Tarreau wrote:
> Hi Thomas,
>
> On Wed, Aug 19, 2026 at 08:31:53AM +0200, Thomas Weißschuh wrote:
> > +++ b/tools/include/nolibc/arch-hexagon.h
> > @@ -0,0 +1,164 @@
> > +/* SPDX-License-Identifier: LGPL-2.1 OR MIT */
> > +/*
> > + * hexagon specific definitions for NOLIBC
> > + * Copyright (C) 2026 Thomas Weißschuh <linux@weissschuh.net>
> > + */
> > +
> > +#ifndef _NOLIBC_ARCH_HEXAGON_H
> > +#define _NOLIBC_ARCH_HEXAGON_H
> > +
> > +#include <linux/unistd.h>
> > +
> > +#include "compiler.h"
> > +#include "crt.h"
> > +
> > +/*
> > + * Syscalls for OpenRISC:
> > + * - syscall number is passed in r6
> > + * - arguments are in r0, r1, r2, r3, r4, r5
> > + * - the system call is performed by calling trap0(#1)
> > + * - syscall return value is in r0
> > + */
>
> I'm not familiar with hexagon, but the file is named hexagon and the
> comment speaks about openrisc. Is this a leftover from a copy-paste,
> or is there an untold relation between the two, that would then deserve
> at least an extra line to explain to those who don't know when passing
> by ?
It is indeed a copy-paste error.
Thanks for noticing!
> Other than this detail, while I can't judge for the syscall instructions
> for this arch, I'm fine with the rest of the patch and the series, so
> feel free to add:
>
> Acked-by: Willy Tarreau <w@1wt.eu>
Thanks!
next prev parent reply other threads:[~2026-08-19 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 6:31 [PATCH 0/3] tools/nolibc: hexagon support Thomas Weißschuh
2026-08-19 6:31 ` [PATCH 1/3] tools/nolibc: split the architecture list into multiple lines Thomas Weißschuh
2026-08-19 6:31 ` [PATCH 2/3] selftests/nolibc: prepare for clang-only architectures Thomas Weißschuh
2026-08-19 6:31 ` [PATCH 3/3] tools/nolibc: add support for hexagon Thomas Weißschuh
2026-08-19 7:12 ` Willy Tarreau
2026-08-19 18:29 ` Thomas Weißschuh [this message]
2026-08-19 14:18 ` [PATCH 0/3] tools/nolibc: hexagon support Brian Cain
2026-08-19 18:30 ` Thomas Weißschuh
2026-08-20 15:24 ` Brian Cain
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=55da1de0-b034-4b3a-8b25-e4cedfeb4418@t-8ch.de \
--to=linux@weissschuh.net \
--cc=bcain@kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®