From: Krzysztof Kozlowski <krzk@kernel.org>
To: Christoph Zimmermann <nussgipfel@brain4free.org>,
Linux CH <lch@lists.linux.dev>
Subject: Re: In search for reviewer/tester for Risc-V JH7110/Star64
Date: Mon, 13 Jan 2025 10:11:07 +0100 [thread overview]
Message-ID: <105e6a2d-5d5d-42ec-810c-649d421d4ecd@kernel.org> (raw)
In-Reply-To: <20250112202110.64d3a9d2@fastfrinz>
On 12/01/2025 20:21, Christoph Zimmermann wrote:
> Hi
>
> I ask here for a friend. He achieved quite some progress in bringing
> missing pieces of the Risc-V JH7110 SoC to mainline and/or bugfixing
> dts stuff.
>
> Problem is now that he needs reviewers/testers and it seems that only
> few can do that or are missing hardware.
>
> "they need participation, even if it is only "Tested-by"
I forwarded your message to friend who does some work around mainline
RISC-V and was looking for some involvement, although nothing related to
Switzerland so no hardware shipment.
> some of the patches need a deep understanding of JH7110, and it may be
> such technical knowledge that a competent Linux developer will give us
> advice how we can find answers for our questions most of the patches
> are simple and can be easily examined and tested for, if having JH7110
> hardware (like Star64) one example of easy to test
> patch: https://lore.kernel.org/lkml/20250102194530.418127-5-e@freeshell.de/
> "
I won't have time, but I admit that such projects are tempting - still
small community. Not like Rpi, where you send a patch and then discover
that 10 people already were working on this feature. :)
Best regards,
Krzysztof
prev parent reply other threads:[~2025-01-13 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 19:21 In search for reviewer/tester for Risc-V JH7110/Star64 Christoph Zimmermann
2025-01-13 9:11 ` Krzysztof Kozlowski [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=105e6a2d-5d5d-42ec-810c-649d421d4ecd@kernel.org \
--to=krzk@kernel.org \
--cc=lch@lists.linux.dev \
--cc=nussgipfel@brain4free.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.