From: "Rutvij Trivedi" <rutvij.trivedi@siliconsignals.io>
To: u-boot-amlogic@groups.io
Subject: S905D3 SOC contribution tips
Date: Sat, 21 Oct 2023 11:31:18 -0700 [thread overview]
Message-ID: <OLZU.1697913078920314417.bpks@groups.io> (raw)
Hello everyone,
I'm a newcomer here and I'm enthusiastic about contributing. I have an SBC based on S905D3.
I want to start contributing, perhaps by tackling smaller tasks, and then gradually, as I understand the ecosystem better, move on to more significant ones.
Could someone suggest some small issues I can start with? Or anything known that I can take up?
Your advice is greatly appreciated.
Best regards,
reply other threads:[~2023-10-22 7:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=OLZU.1697913078920314417.bpks@groups.io \
--to=rutvij.trivedi@siliconsignals.io \
--cc=u-boot-amlogic@groups.io \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).