From: Ivan D <ivdivd0@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: KernelProjects still alive?
Date: Thu, 22 Aug 2019 17:59:45 +0300 [thread overview]
Message-ID: <CADAXeK256YhSqtKTpBdaxv0OAijpQtF4HNxV=JJEYJbfHjYMuA@mail.gmail.com> (raw)
Hi all,
I'd like to do some kernel development (driver, non-trivial feature,
etc.). I'm fairly experienced overall and wrote proprietary kernel
modules at my job, so not interested in newbie/janitor stuff.
KernelProjects looked like a perfect place for this, but it seems long
abandoned.
Is there a substitute, or may be someone can pinpoint me at something
to work on in particular? Could be support for old but still
possible-to-buy hardware, or anything non-trivial really. I've worked
mostly with ARM if that matters, including fairly low level things.
Thanks,
Ivan
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2019-08-22 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 14:59 Ivan D [this message]
2019-08-22 16:27 ` KernelProjects still alive? Greg KH
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='CADAXeK256YhSqtKTpBdaxv0OAijpQtF4HNxV=JJEYJbfHjYMuA@mail.gmail.com' \
--to=ivdivd0@gmail.com \
--cc=kernelnewbies@kernelnewbies.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 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 NNTP newsgroup(s).