From: Phillip Potter <phil@philpotter.co.uk>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Greg KH <gregkh@linuxfoundation.org>,
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 23:12:08 +0100 [thread overview]
Message-ID: <CAA=Fs0=bgZj6jtS3NsfB1kk4TX5BuoN3S5pg9jmnkPPVFYYgpQ@mail.gmail.com> (raw)
In-Reply-To: <e91cf326-f393-4ad5-568a-dbdd7cc759db@lwfinger.net>
On Thu, 22 Jul 2021 at 17:31, Larry Finger <Larry.Finger@lwfinger.net> wrote:
>
> On 7/22/21 8:28 AM, Greg KH wrote:
> > 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?
>
> I am not opposed to that. Do you want me to supply the new driver as a set of
> patches, or would someone else like to do it?
>
> Larry
>
I am happy to do it. Two patches seems sensible - one to remove the
current driver from staging and another to introduce the new one.
Regards,
Phil
next prev parent reply other threads:[~2021-07-22 22:12 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
2021-07-22 16:30 ` Larry Finger
2021-07-22 22:12 ` Phillip Potter [this message]
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='CAA=Fs0=bgZj6jtS3NsfB1kk4TX5BuoN3S5pg9jmnkPPVFYYgpQ@mail.gmail.com' \
--to=phil@philpotter.co.uk \
--cc=Larry.Finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=fabioaiuto83@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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).