From: Nishant Malpani <nish.malpani25@gmail.com>
To: linux-iio@vger.kernel.org
Subject: [RFC] Open Source Contribution | GSoC 2020
Date: Thu, 5 Mar 2020 00:41:40 +0530 [thread overview]
Message-ID: <3bc4e978-3719-bbfc-2110-81601272a938@gmail.com> (raw)
Hello, IIO!
This is Nishant Malpani, a fourth-year integrated Master's student,
majoring in Electronics and Communications (ECE) engineering, at
International Institute of Information Technology, Bangalore, India
(IIIT-B).
Driven by my thirst to gain knowledge about the Linux kernel and its
various subsystems, I would like to be a part of the IIO community and
receive some insights on how to commence contributing.
Formally, I've done a course on 'Linux Device Driver Development' at my
institute wherein I learnt about the various subsystems in the Linux
kernel of which IIO was one of them. I learnt extensively about IIO
Channels, Triggers, Buffers, Events etc. and further concluded by taking
up MCP3008 ADC as a case-study. I'm familiar with the development
process and initiated my contribution by submitting a naive patch [1]
(although it does need an update). I've also invested some time
completing IIO-related tasks listed on what seems like an outdated page
[2]. I'm aware of the previous conversations undertaken in this mailing
list [3] but I wasn't sure if somebody is already working on it. I'd be
delighted to contribute to any of the open tasks!
Thank you all for your time.
With regards,
Nishant Malpani
[1] https://marc.info/?l=linux-driver-devel&m=158326078122615&w=2
[2] https://kernelnewbies.org/IIO_tasks
[3] https://marc.info/?l=linux-iio&m=158257639113000&w=2
next reply other threads:[~2020-03-04 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 19:11 Nishant Malpani [this message]
2020-03-07 16:14 ` [RFC] Open Source Contribution | GSoC 2020 Jonathan Cameron
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=3bc4e978-3719-bbfc-2110-81601272a938@gmail.com \
--to=nish.malpani25@gmail.com \
--cc=linux-iio@vger.kernel.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