linux-staging.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Phillip Potter <phil@philpotter.co.uk>,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	linux-staging@lists.linux.dev, fabioaiuto83@gmail.com
Subject: Re: [PATCH resend] staging: rtl8188eu: move all source files from core subdirectory
Date: Wed, 21 Jul 2021 21:28:36 +0300	[thread overview]
Message-ID: <20210721182836.GX1931@kadam> (raw)
In-Reply-To: <0c2d97fa-e1e1-3564-98b8-37d5b9a1a9cb@lwfinger.net>

On Wed, Jul 21, 2021 at 12:33:28PM -0500, Larry Finger wrote:
> On 7/21/21 2:49 AM, Phillip Potter wrote:
> > Dear Larry,
> > 
> > Whilst I (and no doubt others) are happy to look into what you've
> > suggested, I do have a few questions:
> > (1) Why is the version from github not the one in staging?
> > (2) On a related note, working on it offline is difficult in terms of
> > proving contributions, particularly for a kernel mentee such as myself.
> > 
> > Might I suggest replacing this driver with the one you suggested
> > entirely, so work on it can continue in public? I am happy to submit
> > this and continue work if you think it would be viable. Many thanks and
> > I appreciate your thoughts on this.
> 
> The reason that the newer driver is at GitHub, rather than in the kernel, is
> that I never want to devote the 6 months needed to get it into the shape of
> the old one that I did send to staging. If you take a little time to look at
> the GitHub code, you will see what I mean. I did this once before only to
> have Realtek release a new version with all the old warts again. At least we
> have the fact that this is a heritage product, and Realtek will not be
> releasing any newer drivers.

You're obviously not a Realtek employee, but what are they doing for
wireless drivers these days?

regards,
dan carpenter

  reply	other threads:[~2021-07-21 18: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 [this message]
2021-07-21 19:18             ` Larry Finger
2021-07-22 10:44               ` Phillip Potter
2021-07-22 13:28                 ` Greg KH
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=20210721182836.GX1931@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=fabioaiuto83@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;
as well as URLs for NNTP newsgroup(s).