kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Len Baker <len.baker@gmx.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, kernelnewbies@kernelnewbies.org
Subject: Contributing to drivers/staging area
Date: Fri, 20 Aug 2021 16:45:15 +0200	[thread overview]
Message-ID: <20210820144515.GA5479@titan> (raw)

Hi Greg,

I am a kernel newbie in the path to find an area where to contribute
on. I have sent some patches before (simple ones) but I would like
to find some driver to contribute on and if possible mantain in the
future. Due to the big amount of drivers in staging, and my lack
of experience and specific hardware:

Are there any driver in the staging area that not requires specific
hardware? I have only access to an old laptop with 4 processors:

vendor_id	: GenuineIntel
cpu family	: 6
model		: 37
model name	: Intel(R) Core(TM) i3 CPU       M 370  @ 2.40GHz

Can I find a driver to contribute on with my machine requirements?
If yes, any advise to select one would be greatly appreciated.

I would like to improve the driver until get it out from staging ;)
And then maintain it.

Another option for me if there are no drivers would be create one
from zero. But I don't have any idea of useful driver. Any advise
and ideas here would be also great appreciated.

Thanks in advance.

Regards,
Len

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

             reply	other threads:[~2021-08-20 19:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 14:45 Len Baker [this message]
2021-08-26  8:39 ` Contributing to drivers/staging area Greg KH
2021-08-27 16:56   ` Len Baker

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=20210820144515.GA5479@titan \
    --to=len.baker@gmx.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-kernel@vger.kernel.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).