From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Luca Ceresoli <luca.ceresoli@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/rtl8188eu: remove wrong description in Config.in
Date: Sun, 30 Oct 2022 21:06:15 +0100 [thread overview]
Message-ID: <20221030210615.49866828@windsurf> (raw)
In-Reply-To: <20221019134823.12594-1-giulio.benetti@benettiengineering.com>
On Wed, 19 Oct 2022 15:48:23 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> This rtl8188eu driver is not the same as the one in mainline Linux that
> still has pending work to be done that in this driver is done, check:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/staging/r8188eu/TODO
> specifically:
> * Switch to use LIB80211.
> * Switch to use MAC80211.
> * Switch to use CFG80211.
> So let's remove the description that is not valid anymore.
>
> Suggested-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
> V1->V2:
> * improve Config.in description as pointed by Luca Ceresoli
> ---
> package/rtl8188eu/Config.in | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/package/rtl8188eu/Config.in b/package/rtl8188eu/Config.in
> index 76d9085297..2fab1fd5c0 100644
> --- a/package/rtl8188eu/Config.in
> +++ b/package/rtl8188eu/Config.in
> @@ -4,9 +4,10 @@ config BR2_PACKAGE_RTL8188EU
> depends on BR2_LINUX_KERNEL
> help
> A standalone driver for the RTL8188EU USB Wi-Fi adapter.
> - This is needed only for Linux kernels before 3.12.
> - Since 3.12, there is a (staging) driver in mainline, with a
> - similar codebase.
> + This rtl8188eu driver is not the same as the one in mainline
> + Linux that still has pending work to be done that in this
> + driver is done, check:
> + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/staging/r8188eu/TODO
I don't see any thing in this TODO that explains why the out-of-tree
driver is better than the mainline driver.
The out-of-tree driver has been integrated into drivers/staging/, and
this TODO file lists what should be improved in the driver so that it
can be graduated to move outside of drivers/staging/ into the proper
drivers/net/wireless/ location.
I don't see anything in this TODO that indicates that the out-of-tree
driver has "more features" than the mainline driver, so to me the
Config.in help text still makes sense.
Could you give some more details?
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-10-30 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 13:48 [Buildroot] [PATCH v2] package/rtl8188eu: remove wrong description in Config.in Giulio Benetti
2022-10-19 16:15 ` Luca Ceresoli via buildroot
2022-10-30 20:06 ` Thomas Petazzoni via buildroot [this message]
2022-11-16 0:33 ` Giulio Benetti
2022-11-16 1:15 ` Giulio Benetti
2022-11-16 8:34 ` Luca Ceresoli via buildroot
2022-11-17 19:57 ` Giulio Benetti
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=20221030210615.49866828@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=luca.ceresoli@bootlin.com \
--cc=thomas.petazzoni@bootlin.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