From: Hayes Wang <hayeswang@realtek.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "kuba@kernel.org" <kuba@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
nic_swsd <nic_swsd@realtek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: RE: [PATCH net-next RESEND 2/2] r8152: separate the r8152.c into r8152_main.c and r8152_fw.c
Date: Mon, 26 Jul 2021 11:43:46 +0000 [thread overview]
Message-ID: <13e5ff767f304e1db6b755c10ae47c92@realtek.com> (raw)
In-Reply-To: <YP6Y+i5VzZOJjoW7@kroah.com>
Greg KH <gregkh@linuxfoundation.org>
> Sent: Monday, July 26, 2021 7:14 PM
[...]
> > We support a new chip or feature with a test driver.
> > The test driver is similar with the upstream driver, except
> > the method of the firmware. After we confirm that the
> > test driver work fine, we compare the differences with
> > the upstream driver and submit patches. And the code
> > about firmware takes us more time to find out the
> > differences. Therefore, I wish to move the part of
> > the firmware out.
>
> Great, then submit the broken up driver as part of a patchset that adds
> new device support, as that makes more sense when that happens, right?
I got it. I will submit them with the support of new device in the future.
Best Regards,
Hayes
next prev parent reply other threads:[~2021-07-26 11:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 8:54 [PATCH u-boot 0/2] eth/r8152: minor corrections Hayes Wang
2021-07-13 9:18 ` [PATCH net-next 1/2] r8152: group the usb ethernet of realtek Hayes Wang
2020-05-22 8:54 ` [PATCH u-boot 1/2] eth/r8152: fix assigning the wrong endpoint Hayes Wang
2021-07-13 9:18 ` [PATCH net-next 2/2] r8152: separate the r8152.c into r8152_main.c and r8152_fw.c Hayes Wang
2020-05-22 13:21 ` [PATCH u-boot 1/2] eth/r8152: fix assigning the wrong endpoint Marek Vasut
2020-05-25 3:11 ` Hayes Wang
2020-05-22 8:54 ` [PATCH u-boot 2/2] eth/r8152: fix typo in register name Hayes Wang
2021-07-26 4:01 ` [PATCH net-next RESEND 0/2] r8152: split the source code Hayes Wang
2020-05-22 13:23 ` [PATCH u-boot 2/2] eth/r8152: fix typo in register name Marek Vasut
2020-05-25 7:47 ` [PATCH u-boot v2 0/2] eth/r8152: minor corrections Hayes Wang
2021-07-26 4:01 ` [PATCH net-next RESEND 1/2] r8152: group the usb ethernet of realtek Hayes Wang
2020-05-25 7:47 ` [PATCH u-boot v2 1/2] eth/r8152: fix assigning the wrong endpoint Hayes Wang
2021-07-26 4:01 ` [PATCH net-next RESEND 2/2] r8152: separate the r8152.c into r8152_main.c and r8152_fw.c Hayes Wang
2020-05-25 12:03 ` [PATCH u-boot v2 1/2] eth/r8152: fix assigning the wrong endpoint Marek Vasut
2020-05-25 12:52 ` Hayes Wang
2020-05-25 13:00 ` Marek Vasut
2020-05-26 1:59 ` Hayes Wang
2021-07-26 7:36 ` [PATCH net-next RESEND 2/2] r8152: separate the r8152.c into r8152_main.c and r8152_fw.c Greg KH
2021-07-26 8:26 ` Hayes Wang
2021-07-26 8:37 ` Greg KH
2021-07-26 11:09 ` Hayes Wang
2021-07-26 11:14 ` Greg KH
2021-07-26 11:43 ` Hayes Wang [this message]
2020-05-25 7:47 ` [PATCH u-boot v2 2/2] eth/r8152: fix typo in register name Hayes Wang
-- strict thread matches above, loose matches on Subject: below --
2021-07-13 9:18 [PATCH net-next 0/2] r8152: split the source code Hayes Wang
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=13e5ff767f304e1db6b755c10ae47c92@realtek.com \
--to=hayeswang@realtek.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.