Linux kernel staging patches
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Peter Robinson <pbrobinson@gmail.com>
Cc: linux-staging@lists.linux.dev
Subject: Re: [PATCH 1/4] staging: rtl8192u: Provide a TODO file for this driver
Date: Thu, 20 Oct 2022 17:49:50 +0200	[thread overview]
Message-ID: <Y1FuHoeNNcUhNSpB@kroah.com> (raw)
In-Reply-To: <20221016110743.1448067-1-pbrobinson@gmail.com>

On Sun, Oct 16, 2022 at 12:07:40PM +0100, Peter Robinson wrote:
> Provide a TODO file that lists the tasks that should be carried out in
> order to move this driver off drivers/staging. It's missing from original
> addition of this driver.
> 
> Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
> ---
>  drivers/staging/rtl8192u/TODO | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
>  create mode 100644 drivers/staging/rtl8192u/TODO
> 
> diff --git a/drivers/staging/rtl8192u/TODO b/drivers/staging/rtl8192u/TODO
> new file mode 100644
> index 000000000000..ab9d5d145b3b
> --- /dev/null
> +++ b/drivers/staging/rtl8192u/TODO
> @@ -0,0 +1,16 @@
> +To-do list:
> +
> +* Correct the coding style according to Linux guidelines; please read the document
> +  at https://www.kernel.org/doc/html/latest/process/coding-style.html.
> +* Remove unnecessary debugging/printing macros; for those that are still needed
> +  use the proper kernel API (pr_debug(), dev_dbg(), netdev_dbg()).
> +* Remove dead code such as unusued functions, variables, fields, etc..
> +* Use in-kernel API and remove unnecessary wrappers where possible.
> +* Fix bugs due to code that sleeps in atomic context.
> +* Remove the HAL layer and migrate its functionality into the relevant parts of
> +  the driver.
> +* Switch to use LIB80211.
> +* Switch to use MAC80211.
> +* Switch to use CFG80211.
> +* Improve the error handling of various functions, particularly those that use
> +  existing kernel APIs.

Where did this list come from?

How do you know they are all needed?

thanks,

greg k-h

  parent reply	other threads:[~2022-10-20 15:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16 11:07 [PATCH 1/4] staging: rtl8192u: Provide a TODO file for this driver Peter Robinson
2022-10-16 11:07 ` [PATCH 2/4] staging: rtl8192e: Update the " Peter Robinson
2022-10-16 11:07 ` [PATCH 3/4] staging: ks7010: " Peter Robinson
2022-10-16 11:07 ` [PATCH 4/4] staging: wlan-ng: Provide a " Peter Robinson
2022-10-20 15:49 ` Greg Kroah-Hartman [this message]
2022-10-20 15:57   ` [PATCH 1/4] staging: rtl8192u: " Peter Robinson

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=Y1FuHoeNNcUhNSpB@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=pbrobinson@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