From: Albert Zhou <albert.zhou.50@gmail.com>
To: Hayes Wang <hayeswang@realtek.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
nic_swsd <nic_swsd@realtek.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next RFC 0/5] Update r8152 to version two
Date: Wed, 9 Nov 2022 22:20:21 +1100 [thread overview]
Message-ID: <9539bd4d-ee52-5148-73fd-3753dd5a616d@gmail.com> (raw)
In-Reply-To: <77e816857bbd46ec8357134f767be785@realtek.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1137 bytes --]
On 9/11/22 22:02, Hayes Wang wrote:
> Albert Zhou<albert.zhou.50@gmail.com>
>> Sent: Tuesday, November 8, 2022 11:34 PM
>> Subject: [PATCH net-next RFC 0/5] Update r8152 to version two
>>
>> This patch integrates the version-two r8152 drivers from Realtek into
>> the kernel. I am new to kernel development, so apologies if I make
>> newbie mistakes.
> The Realtek's in-house driver doesn't satisfy the rules or requests of
> Linux kernel, so I don't think you could use it to replace the Linux
> kernel r8152 driver.
>
> The version is used to distinguish between the Realtek's in-house driver
> and Linux kernel r8152 driver. It doesn't mean you have to use version 2,
> even the version 2 may contain more experiment features.
>
> Best Regards,
> Hayes
>
Thanks for clarifying this, and thanks Greg for your advice in the
previous message. I will follow Greg's advice and try and identify that
bits of code that fixes my issue of having throttled data-transfer speed
via ethernet.
If you have some kind of in-house changelog that you could make
available to me, I would be grateful.
Best,
Albert
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 653 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2022-11-09 11:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 15:33 [PATCH net-next RFC 0/5] Update r8152 to version two Albert Zhou
2022-11-08 15:33 ` [PATCH net-next RFC 1/5] net: move back netif_set_gso_max helpers Albert Zhou
2022-11-08 17:27 ` Greg KH
2022-11-08 15:33 ` [PATCH net-next RFC 2/5] r8152: update to version two Albert Zhou
2022-11-08 17:28 ` Greg KH
2022-11-09 4:50 ` Albert Zhou
2022-11-09 7:42 ` Greg KH
2022-11-08 15:33 ` [PATCH net-next RFC 3/5] r8152: remove backwards compatibility Albert Zhou
2022-11-08 15:33 ` [PATCH net-next RFC 4/5] r8152: merge header into source Albert Zhou
2022-11-08 15:33 ` [PATCH net-next RFC 5/5] r8152: remove redundant code Albert Zhou
2022-11-08 20:50 ` [PATCH net-next RFC 0/5] Update r8152 to version two Jakub Kicinski
2022-11-09 4:43 ` Albert Zhou
2022-11-09 18:40 ` Jakub Kicinski
2022-11-16 15:13 ` Albert Zhou
2022-11-16 16:34 ` Jakub Kicinski
2022-11-08 21:03 ` Francois Romieu
2022-11-09 4:54 ` Albert Zhou
2022-11-09 11:02 ` Hayes Wang
2022-11-09 11:20 ` Albert Zhou [this message]
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=9539bd4d-ee52-5148-73fd-3753dd5a616d@gmail.com \
--to=albert.zhou.50@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hayeswang@realtek.com \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=pabeni@redhat.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 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).