From: Fabio Aiuto <fabioaiuto83@gmail.com>
To: Phillip Potter <phil@philpotter.co.uk>
Cc: gregkh@linuxfoundation.org, Larry.Finger@lwfinger.net,
dan.carpenter@oracle.com, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH 6/7] staging: rtl8188eu: introduce new supporting files for RTL8188eu driver
Date: Fri, 23 Jul 2021 09:29:36 +0200 [thread overview]
Message-ID: <20210723072936.GA1613@agape.jhs> (raw)
In-Reply-To: <20210723004214.912295-7-phil@philpotter.co.uk>
Hello Phillip,
On Fri, Jul 23, 2021 at 01:42:13AM +0100, Phillip Potter wrote:
> This patchset is split in order to keep the file sizes down. These
> supporting files are part of the newer/better driver from GitHub modified by
> Larry Finger. Import this as the basis for all future work going
> forward. Also, modify Makefile so that driver has same module filename
> as original rtl8188eu driver from staging.
>
> Suggested-by: Larry Finger <Larry.Finger@lwfinger.net>
> Signed-off-by: Phillip Potter <phil@philpotter.co.uk>
> ---
> drivers/staging/rtl8188eu/COPYING | 356 ++++++++++++++++++++
> drivers/staging/rtl8188eu/Kconfig | 25 ++
> drivers/staging/rtl8188eu/Makefile | 509 +++++++++++++++++++++++++++++
> 3 files changed, 890 insertions(+)
> create mode 100644 drivers/staging/rtl8188eu/COPYING
> create mode 100644 drivers/staging/rtl8188eu/Kconfig
> create mode 100755 drivers/staging/rtl8188eu/Makefile
Nice work...
a new TODO file is needed.
@Larry, maybe you can help us telling what's needed
to mainline this new rtl8188eu.
thank you,
fabio
next prev parent reply other threads:[~2021-07-23 7:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 0:42 [PATCH 0/7] staging: rtl8188eu: replace driver with better version Phillip Potter
2021-07-23 0:42 ` [PATCH 1/7] staging: rtl8188eu: remove existing staging driver Phillip Potter
2021-07-23 0:42 ` [PATCH 2/7] staging: rtl8188eu: introduce new core dir for RTL8188eu driver Phillip Potter
2021-07-23 0:42 ` [PATCH 3/7] staging: rtl8188eu: introduce new hal " Phillip Potter
2021-07-23 0:42 ` [PATCH 4/7] staging: rtl8188eu: introduce new os_dep " Phillip Potter
2021-07-23 17:33 ` kernel test robot
2021-07-23 17:33 ` kernel test robot
2021-07-23 17:33 ` [RFC PATCH] staging: rtl8188eu: fix duplicated inclusion kernel test robot
2021-07-23 17:33 ` kernel test robot
2021-07-23 0:42 ` [PATCH 5/7] staging: rtl8188eu: introduce new include dir for RTL8188eu driver Phillip Potter
2021-07-23 0:42 ` [PATCH 6/7] staging: rtl8188eu: introduce new supporting files " Phillip Potter
2021-07-23 7:29 ` Fabio Aiuto [this message]
2021-07-23 11:09 ` Greg KH
2021-07-23 11:19 ` Phillip Potter
2021-07-23 0:42 ` [PATCH 7/7] staging: rtl8188eu: attach newly imported driver to build system Phillip Potter
2021-07-23 7:19 ` kernel test robot
2021-07-23 7:19 ` kernel test robot
2021-07-23 14:33 ` kernel test robot
2021-07-23 14:33 ` kernel test robot
2021-07-23 1:56 ` [PATCH 0/7] staging: rtl8188eu: replace driver with better version Larry Finger
2021-07-23 7:29 ` Phillip Potter
2021-07-23 11:01 ` Greg KH
2021-07-23 11:05 ` Phillip Potter
2021-07-23 21:08 ` Larry Finger
2021-07-23 21:27 ` 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=20210723072936.GA1613@agape.jhs \
--to=fabioaiuto83@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=dan.carpenter@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.