From: Brian Cain <brian.cain@oss.qualcomm.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Brian Cain <bcain@kernel.org>, Willy Tarreau <w@1wt.eu>,
Shuah Khan <shuah@kernel.org>,
linux-hexagon@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, rob@landley.net
Subject: Re: [PATCH 0/3] tools/nolibc: hexagon support
Date: Thu, 20 Aug 2026 10:24:56 -0500 [thread overview]
Message-ID: <41d88b1d-38a2-4a34-9cbe-4a2feca29999@oss.qualcomm.com> (raw)
In-Reply-To: <944f4ad4-6473-4058-b0da-25f9ed45cfae@t-8ch.de>
On 8/19/2026 1:30 PM, Thomas Weißschuh wrote:
> On 2026-08-19 09:18:08-0500, Brian Cain wrote:
>> On 8/19/2026 1:31 AM, Thomas Weißschuh wrote:
>>> Add support for the hexagon architecture.
>>>
>>> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
>>> ---
>>
>> Thanks, Thomas! I've got similar nolibc patches in my tree that I have been
>> sitting on - but I like yours better.
> Out of curiosity, are you using the hexagon nolibc actively or was it
> just for fun?
I have some patches to enable booting the kernel on qemu-system-hexagon
and when I shared them with Rob Landley he suggested I give it a try.
So I did :)
>
>> Aside from the copy/paste error Willy identified, LGTM:
>>
>> Reviewed-by: Brian Cain <brian.cain@oss.qualcomm.com>
> Thanks!
prev parent reply other threads:[~2026-08-20 15:25 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
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 [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=41d88b1d-38a2-4a34-9cbe-4a2feca29999@oss.qualcomm.com \
--to=brian.cain@oss.qualcomm.com \
--cc=bcain@kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=rob@landley.net \
--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