public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Phillip Potter <phil@philpotter.co.uk>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-staging@lists.linux.dev,
	Fabio Aiuto <fabioaiuto83@gmail.com>
Subject: Re: [PATCH resend] staging: rtl8188eu: move all source files from core subdirectory
Date: Thu, 22 Jul 2021 15:28:06 +0200	[thread overview]
Message-ID: <YPlyZsuRJpkUwWiJ@kroah.com> (raw)
In-Reply-To: <CAA=Fs0nvhxEhJhCTWH_KkYyB3Jz7Pi-t2a+6zL3K=O-_3-sLGg@mail.gmail.com>

On Thu, Jul 22, 2021 at 11:44:10AM +0100, Phillip Potter wrote:
> On Wed, 21 Jul 2021 at 20:18, Larry Finger <Larry.Finger@lwfinger.net> wrote:
> >
> > On 7/21/21 1:28 PM, Dan Carpenter wrote:
> > > You're obviously not a Realtek employee, but what are they doing for
> > > wireless drivers these days?
> >
> > You are correct in that I am not a Realtek employee, nor do I have any knowledge
> > of the internals of any of their chips. I do have a close working arrangement
> > with the head of their PCI driver development, and I have gotten free samples of
> > some of their chips. I am a volunteer that is interested in providing drivers
> > for the devices in new laptops with wireless chips that do not yet have a Linux
> > driver in the kernel. I also provide relatively modern drivers for older USB
> > devices through GitHub repos.
> >
> >  From what I know, the PCI group at Realtek is mainly working on new 802.11ac
> > devices, but are leaving some hooks for the USB and SDIO equivalents of those
> > chips (RTL8822BE, RTL8822CE, RTL8821CE, RTL8723DE, and RTL8852AE). These drivers
> > are either in the drivers/net/wireless tree of the kernel, or are under review
> > for such inclusion.
> >
> > I have no current contact with the USB part of their driver development.
> >
> > Larry
> >
> >
> Dear Larry,
> 
> Thank you for this info, it's very useful. Are you saying that in its
> current state the GitHub driver would not even be accepted into
> staging in your opinion? I am happy to continue improving it, but in
> my mind this should probably be done publicly, within the kernel tree.
> Not sure what others think but if there is general consensus then I
> can submit this new version to staging and integrate within build
> framework etc, then we can start improving it and getting it ready to
> move beyond that. Sounds like your driver is further along the path,
> and we should be using it, but I'm interested in what others think of
> course.

If the code looks "better", I have no objection to just adding it to
drivers/staging/ and deleting the existing one here, so that everyone
can work on this together in one single place.

Larry, any objection to that?

thanks,

greg k-h

  reply	other threads:[~2021-07-22 13:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 22:46 [PATCH resend] staging: rtl8188eu: move all source files from core subdirectory Phillip Potter
2021-07-19 23:46 ` Larry Finger
2021-07-20  9:00   ` Fabio Aiuto
2021-07-20 22:54     ` Phillip Potter
2021-07-21  7:51       ` Fabio Aiuto
2021-07-21  0:22     ` Larry Finger
2021-07-21  7:47       ` Fabio Aiuto
2021-07-21  7:49       ` Phillip Potter
2021-07-21 17:33         ` Larry Finger
2021-07-21 18:28           ` Dan Carpenter
2021-07-21 19:18             ` Larry Finger
2021-07-22 10:44               ` Phillip Potter
2021-07-22 13:28                 ` Greg KH [this message]
2021-07-22 16:30                   ` Larry Finger
2021-07-22 22:12                     ` Phillip Potter
2021-07-20 22:51   ` Phillip Potter
2021-07-21  8:16 ` Greg KH

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=YPlyZsuRJpkUwWiJ@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=dan.carpenter@oracle.com \
    --cc=fabioaiuto83@gmail.com \
    --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