From: ShiHao <i.shihao.999@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: ShiHao <i.shihao.999@gmail.com>,
marcelo.schmitt@analog.com, jic23@kernel.org,
dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
mazziesaccount@gmail.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, till@linux.com
Subject: Re: Request for guidence
Date: Wed, 11 Mar 2026 10:43:19 +0530 [thread overview]
Message-ID: <abD572bpEU8f9Uil@fedora> (raw)
In-Reply-To: <aa_yTUNAmkOUnN7j@ashevche-desk.local>
On Tue, Mar 10, 2026 at 12:28:29PM +0200, Andy Shevchenko wrote:
> We are already in the relevant mailing list, so if ShiHao wants to work on IIO
> drivers, welcome!
> With Best Regards,
> Andy Shevchenko
>
>
Hello,
First of all, thank you all for your time and responses. After
learning that the IIO driver development project will not be
part of this year’s GSoC, I shifted my preparation toward the
DT binding project idea since it aligns with my driver development
goals and Thank you, Andy, for letting me know that I can still
work on driver development. However, I still have no clear idea
how to get started.
My main questions are: how should I begin, which sensors currently
need drivers, and what happens if someone else is already working
on a particular driver? Would it still be possible for me to
contribute?
Therefore, I would really appreciate some guidance on how to get
started. Any help would be greatly appreciated. Thank you all again.
With sincere regards,
Shi Hao
next prev parent reply other threads:[~2026-03-11 5:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 5:18 Request for guidence ShiHao
2026-03-07 21:43 ` Marcelo Schmitt
2026-03-09 22:55 ` Till Kamppeter
2026-03-10 10:28 ` Andy Shevchenko
2026-03-11 5:13 ` ShiHao [this message]
2026-03-22 12:06 ` Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2026-03-18 12:32 request " ShiHao
2026-03-18 12:53 ` Krzysztof Kozlowski
2026-03-18 13:42 ` ShiHao
2026-03-18 14:15 ` Krzysztof Kozlowski
2026-03-19 9:17 ` ShiHao
2026-03-19 9:27 ` Krzysztof Kozlowski
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=abD572bpEU8f9Uil@fedora \
--to=i.shihao.999@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt@analog.com \
--cc=mazziesaccount@gmail.com \
--cc=nuno.sa@analog.com \
--cc=till@linux.com \
/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