[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47801164b7b3406b895be1542e0ce4a2@realtek.com>
Date: Mon, 26 Jul 2021 11:09:06 +0000
From: Hayes Wang <hayeswang@...ltek.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: "kuba@...nel.org" <kuba@...nel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
nic_swsd <nic_swsd@...ltek.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>
Subject: RE: [PATCH net-next RESEND 2/2] r8152: separate the r8152.c into r8152_main.c and r8152_fw.c
Greg KH <gregkh@...uxfoundation.org>
> Sent: Monday, July 26, 2021 4:37 PM
[...]
> You also do other things, like renaming defines, which is not just
> moving code around, right?
Yes. You are right.
[...]
> I do not know, is it really easier to find things in 3 different files
> instead of one? That's up to you, but you did not say why this change
> is needed.
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.
I don't sure if it is acceptable for such patches.
If it is unacceptable, I would abandon these patches.
Best Regards,
Hayes
Powered by blists - more mailing lists