From: Sidong Yang <realwakka@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: A question about staging driver like pi433
Date: Thu, 12 Aug 2021 07:43:58 +0000 [thread overview]
Message-ID: <20210812074358.GA37154@realwakka> (raw)
In-Reply-To: <YRIY3q39j/b5O3Ir@kroah.com>
On Tue, Aug 10, 2021 at 08:12:46AM +0200, Greg KH wrote:
> On Mon, Aug 09, 2021 at 11:27:13PM +0000, Sidong Yang wrote:
> > On Mon, Aug 09, 2021 at 08:20:03PM +0200, Greg KH wrote:
> > > On Mon, Aug 09, 2021 at 04:13:28PM +0000, Sidong Yang wrote:
> > > > Hi all,
> > > >
> > > > I have a question about staging driver. I'm a newbie kernel developer
> > > > and I tried contributed some patches for staging drivers. In those
> > > > staging drivers, I'm interested in pi433 and wrote some patches for it
> > > > about 2 years ago. and then I tried to go deeper for that. I tried to
> > > > buy pi433 device but I can't. It seems that no longer available.
> > > >
> > > > In this case, pi433 should be removed from source tree?
> > >
> > > Why would it be removed if people still use it?
> >
> > Yeah, I thought there is no user using this device. I realized that it
> > was bad idea.
>
> Is there no one using this? That's kind of hard to determine, and is
> a problem we have at times :(
I contacted the hardware developer in personal. And He replied positive.
I would get the pi433 device soon. It would be nice that It can be
tested in practice.
Thanks,
Sidong
>
> thanks,
>
> greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2021-08-12 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 16:13 A question about staging driver like pi433 Sidong Yang
2021-08-09 18:20 ` Greg KH
2021-08-09 23:27 ` Sidong Yang
2021-08-10 6:12 ` Greg KH
2021-08-12 7:43 ` Sidong Yang [this message]
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=20210812074358.GA37154@realwakka \
--to=realwakka@gmail.com \
--cc=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).