Linux kernel staging patches
 help / color / mirror / Atom feed
From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Marcus Wolf <linux@wolf-entwicklungen.de>,
	Marcus Wolf <marcus.wolf@wolf-entwicklungen.de>,
	"linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [RFC] staging: pi433: Proposal to remove unused driver
Date: Wed, 27 Mar 2024 22:55:13 +0100	[thread overview]
Message-ID: <c4c5ab38-8c67-4c21-86bc-f4f3c06be358@gmail.com> (raw)

Hi Marcus,

according to this homepage:
https://www.kickstarter.com/projects/1292669042/pi433-a-radio-module-funkmodul-for-raspberry-pi
you had a group of people to test and use the Pi433. But last 
update/comments on this website are from November 21, 2017. What 
happened afterwards? Did you organize the community differently?

On this homepage:
https://www.pi433.de/en.html
you wrote:
"Purchase Pi433
Due to the rules for recycling (WEEE guideline of EU) Smarthome-Wolf 
decided to stop the direct distribution of Pi433.

Business partner (e. g. online stores for selling Raspberry-Pi 
accessories), interested in distribution of Pi433 are very welcome!"

It seems that this was also in 2017

Did you manage to find a business partner?
How many devices have been sold after 2017? Are there people who got 
more than 1 device?

Please respond to avoid that unused code stays in the mainline kernel 
forever.

Thanks for your support.

Bye Philipp

                 reply	other threads:[~2024-03-27 21:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=c4c5ab38-8c67-4c21-86bc-f4f3c06be358@gmail.com \
    --to=philipp.g.hortmann@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=linux@wolf-entwicklungen.de \
    --cc=marcus.wolf@wolf-entwicklungen.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).