All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
To: ShiHao <i.shihao.999@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,
	linux-kernel@vger.kernel.org, till@linux.com
Subject: Re: Request for guidence
Date: Sat, 7 Mar 2026 18:43:53 -0300	[thread overview]
Message-ID: <aaycGSJIQicH34jD@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <aapjuiq0JSVWfmWA@fedora>

Hello ShiHao,

On 03/06, ShiHao wrote:
> hello,
> 
> I hope everyone is doing well and fine. Recently i have been
> getting prepared for gsoc 2026 for The Linux Foundation project
> idea iio AD39113 driver development however i just noticed that the
> project idea has been withdrawn from the list. I wanted to ask that
> whether the driver develpment is still planned or it is dropped from
> project idea list.

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.

https://github.com/LinuxFoundationGSoC/ProjectIdeas/wiki/GSoC-2026-Device-Tree-Bindings

> 
> If the driver is still needed , I would be interested in contribtuting
> to its development outside gsoc as well since i have no idea whether i
> would be allowed for its development or not thats is why  any help would
> be appreciated thank you for your time .
> 

If you're anyway interested in contributing to IIO, there are links to
IIO-related material in the non-active IIO project page

https://github.com/LinuxFoundationGSoC/ProjectIdeas/wiki/GSoC-2026-IIO-Driver

I am unable to send any hardware anywhere, though.

With best regards,
Marcelo

  reply	other threads:[~2026-03-07 21:43 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 [this message]
2026-03-09  4:14   ` ShiHao
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=aaycGSJIQicH34jD@debian-BULLSEYE-live-builder-AMD64 \
    --to=marcelo.schmitt1@gmail.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=i.shihao.999@gmail.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 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.