From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Phillip Potter <phil@philpotter.co.uk>,
"open list:STAGING SUBSYSTEM" <linux-staging@lists.linux.dev>,
open list <linux-kernel@vger.kernel.org>,
Michael Straube <straube.linux@gmail.com>,
Martin Kaiser <martin@kaiser.cx>
Subject: Re: TODO list for staging/r8188eu
Date: Sun, 22 Aug 2021 15:50:14 +0200 [thread overview]
Message-ID: <2099975.VbY6Rib6K3@localhost.localdomain> (raw)
In-Reply-To: <YSJE6aoH96kh777R@kroah.com>
On Sunday, August 22, 2021 2:36:57 PM CEST Greg Kroah-Hartman wrote:
> On Sun, Aug 22, 2021 at 09:41:20AM +0200, Fabio M. De Francesco wrote:
> > Dear Larry, Philip,
> >
> > >From what I understand how the development process works, drivers in
staging
> >
> > should have a to-do list in the TODO file. Please read https://
www.kernel.org/
> > doc/html/latest/process/2.Process.html?highlight=todo#staging-trees.
> >
> > Could you (as the maintainers of the r8188eu driver) please compile and
> > provide the above mentioned list?
>
> Why don't you provide an initial list for people to work off of if you
> feel it is needed here?
>
> thanks,
>
> greg k-h
Unfortunately I'm not able to tell what is needed to do to have a driver
improved so that it can be moved off staging. This work should be better
addressed by someone who is much more experienced.
For example, I read from other drivers TODO lists that cfg80211 and lib80211
are required but I don't know what they are.
Regards,
Fabio
next prev parent reply other threads:[~2021-08-22 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 7:41 TODO list for staging/r8188eu Fabio M. De Francesco
2021-08-22 12:36 ` Greg Kroah-Hartman
2021-08-22 13:50 ` Fabio M. De Francesco [this message]
2021-08-22 14:33 ` Greg Kroah-Hartman
2021-08-22 15:09 ` Phillip Potter
2021-08-22 16:13 ` Fabio M. De Francesco
2021-08-23 0:00 ` Phillip Potter
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=2099975.VbY6Rib6K3@localhost.localdomain \
--to=fmdefrancesco@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin@kaiser.cx \
--cc=phil@philpotter.co.uk \
--cc=straube.linux@gmail.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 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).