From: Pavel Skripkin <paskripkin@gmail.com>
To: Phillip Potter <phil@philpotter.co.uk>, gregkh@linuxfoundation.org
Cc: Larry.Finger@lwfinger.net, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, fabioaiuto83@gmail.com,
fmdefrancesco@gmail.com
Subject: Re: [PATCH] staging: r8188eu: add extra TODO entries
Date: Sat, 28 Aug 2021 13:13:43 +0300 [thread overview]
Message-ID: <4ed7a185-0be2-82cb-5460-73a3e27cd6e7@gmail.com> (raw)
In-Reply-To: <20210828000231.1458-1-phil@philpotter.co.uk>
On 8/28/21 3:02 AM, Phillip Potter wrote:
> Add entry for CFG80211 to reflect that it is currently being worked on
> and is a desirable feature to have for this driver. Leave entries for
> LIB80211 and MAC80211 in case anyone else wishes to work on them - they
> can always be removed later, but MAC80211 in particular would certainly
> be good to aim for. Also, include an entry for improving error handling,
> as this is another goal of the cleanup effort.
>
> Signed-off-by: Phillip Potter <phil@philpotter.co.uk>
> ---
> drivers/staging/r8188eu/TODO | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/staging/r8188eu/TODO b/drivers/staging/r8188eu/TODO
> index 98f918480990..ab9d5d145b3b 100644
> --- a/drivers/staging/r8188eu/TODO
> +++ b/drivers/staging/r8188eu/TODO
> @@ -11,3 +11,6 @@ To-do list:
> 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.
>
Cool, I like it. There is one more extra task, but I will take care of
it. I hope. We need to delete dead proc code and move to sysfs. I have a
plan to finish this part until next weekends, but maybe it worth adding
to TODO.
Thank you
With regards,
Pavel Skripkin
prev parent reply other threads:[~2021-08-28 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-28 0:02 Phillip Potter
2021-08-28 10:13 ` Pavel Skripkin [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=4ed7a185-0be2-82cb-5460-73a3e27cd6e7@gmail.com \
--to=paskripkin@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=fabioaiuto83@gmail.com \
--cc=fmdefrancesco@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=phil@philpotter.co.uk \
/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
all inboxes | Powered by JetHome®