From: ShiHao <i.shihao.999@gmail.com>
To: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
Cc: 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,
i.shihao.999@gmail.com
Subject: Re: Request for guidence
Date: Mon, 9 Mar 2026 09:44:37 +0530 [thread overview]
Message-ID: <aa5JLY7UWrG7-9EN@fedora> (raw)
In-Reply-To: <aaycGSJIQicH34jD@debian-BULLSEYE-live-builder-AMD64>
On Sat, Mar 07, 2026 at 06:43:53PM -0300, Marcelo Schmitt wrote:
> Glad to know about your interest in the IIO driver GSoC project.
> There will be no IIO driver GSoC project this year. I suggest the Device Tree
> Bindings project as an alternative.
> If you're anyway interested in contributing to IIO, there are links to
> IIO-related material in the non-active IIO project page
> I am unable to send any hardware anywhere, though.
>
> With best regards,
> Marcelo
hello, Marcelo Schmitt
Thank you for your kind response . I will surely checkout if there is
any sensor that requires driver because anyway i will make one driver
and i thought it would be good if i could up-stream it but for now i am
preparing for device tree project idea from Linux foundation because it
aligns with my driver development goals therefore if there is any
suggestions or any help i would appreciate it deeply. Thank you all
for you time.
Sincerely
shi Hao
next prev parent reply other threads:[~2026-03-09 4:14 UTC|newest]
Thread overview: 9+ 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 4:14 ` ShiHao [this message]
2026-03-09 22:55 ` Till Kamppeter
2026-03-10 10:28 ` Andy Shevchenko
2026-03-10 14:37 ` Request for guidance ChenLei
2026-03-10 16:54 ` Andy Shevchenko
2026-03-11 5:13 ` Request for guidence ShiHao
2026-03-22 12:06 ` 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=aa5JLY7UWrG7-9EN@fedora \
--to=i.shihao.999@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=marcelo.schmitt@analog.com \
--cc=mazziesaccount@gmail.com \
--cc=nuno.sa@analog.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 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.