linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Philipp Hortmann <philipp.g.hortmann@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org, linux-staging@lists.linux.dev,
	Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH v2 4/6] staging: rtl8192e: delete the driver
Date: Tue, 8 Oct 2024 08:42:21 +0200	[thread overview]
Message-ID: <2024100810-payback-suds-8c15@gregkh> (raw)
In-Reply-To: <b6ff86e3-56a1-43d3-83b2-01818684f076@gmail.com>

On Mon, Oct 07, 2024 at 11:32:25PM +0200, Philipp Hortmann wrote:
> On 10/7/24 20:26, Johannes Berg wrote:
> > From: Johannes Berg<johannes.berg@intel.com>
> > 
> > This driver is using lib80211 and any driver that plans to ever
> > leave staging should never have done that, so remove the driver
> > to enable cleaning up lib80211 into libipw inside the old Intel
> > drivers.
> > 
> > Signed-off-by: Johannes Berg<johannes.berg@intel.com>
> > ---
> 
> Hi Johannes,
> 
> this driver is not only working, it is also supporting a form factor that is
> usable and is available on the used hardware market.
> 
> Is it possible to migrate the driver from lib80211 to libipw?

I don't think a "migration" is simple or easy, I only know of one driver
that ever made that move and it was not easy.  It's simpler to just take
the existing driver, hack it to pieces out-of-tree and then submit a new
driver using the correct apis.

As you have the hardware itself, that would be a good thing to do as you
can test it.

> It does not have to be you who is doing this. How urgent is it to remove
> this driver?

No staging driver should ever get in the way of api changes elsewhere in
the kernel, that's one of the rules of this part of the tree.  So from
my opinion, it's fine to delete it now.  It can always come back in a
new way later on.

thanks,

greg k-h

  reply	other threads:[~2024-10-08  6:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-07 18:26 [PATCH v2 0/6] lib80211 cleanup Johannes Berg
2024-10-07 18:26 ` [PATCH v2 1/6] wifi: qtnfmac: don't include lib80211.h Johannes Berg
2024-10-07 18:26 ` [PATCH v2 2/6] wifi: mwifiex: " Johannes Berg
2024-10-07 18:26 ` [PATCH v2 3/6] wifi: libertas: don't select/include lib80211 Johannes Berg
2024-10-07 18:26 ` [PATCH v2 4/6] staging: rtl8192e: delete the driver Johannes Berg
2024-10-07 21:32   ` Philipp Hortmann
2024-10-08  6:42     ` Greg Kroah-Hartman [this message]
2024-10-08  9:47       ` Johannes Berg
2024-10-08  6:42   ` Greg Kroah-Hartman
2024-10-08 18:12     ` Philipp Hortmann
2024-10-07 18:26 ` [PATCH v2 5/6] wifi: ipw2x00/lib80211: move remaining lib80211 into libipw Johannes Berg
2024-10-07 18:26 ` [PATCH v2 6/6] staging: don't recommend using lib80211 Johannes Berg
2024-10-08 10:15   ` Greg Kroah-Hartman

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=2024100810-payback-suds-8c15@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-staging@lists.linux.dev \
    --cc=linux-wireless@vger.kernel.org \
    --cc=philipp.g.hortmann@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).