linux-kernel - RE: [PATCH] net: phy: realtek: Replace 2.5Gbps name from RTL8125 to RTL8226

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 21 Sep 2020 01:55:23 +0000
From:   劉偉權 <willy.liu@...ltek.com>
To:     Andrew Lunn <andrew@...n.ch>
CC:     "hkallweit1@...il.com" <hkallweit1@...il.com>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "linux@...linux.org.uk" <linux@...linux.org.uk>,
        "kuba@...nel.org" <kuba@...nel.org>,
        Ryan Kao <ryankao@...ltek.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] net: phy: realtek: Replace 2.5Gbps name from RTL8125 to RTL8226

Hi Andrew,
Thanks...understood...

B.R.
Willy
----Original Message-----
From: Andrew Lunn <andrew@...n.ch> 
Sent: Friday, September 18, 2020 10:01 PM
To: 劉偉權 <willy.liu@...ltek.com>
Cc: hkallweit1@...il.com; davem@...emloft.net; linux@...linux.org.uk; kuba@...nel.org; Ryan Kao <ryankao@...ltek.com>; netdev@...r.kernel.org; linux-kernel@...r.kernel.org
Subject: Re: [PATCH] net: phy: realtek: Replace 2.5Gbps name from RTL8125 to RTL8226

On Fri, Sep 18, 2020 at 09:02:43AM +0000, 劉偉權 wrote:
> Hi Andrew,
> Thanks for your information. Should I do any modifications to make this patch be applied?

Please do not to post. And wrap your text to about 75 characters.

Since i think you are new to posting to netdev, we tend to be generous to start with, and allow minor process errors. But we do expect you to learn from what we say, and watch other patches on netdev, so that future patches do follow the processes. So please get [PATCH <tree> v<version>] correct in your next patches, include a summary of what has changed between versions, etc.

I guess David will accept this patch. If not, he will tell you why and what you need to improve.

  Andrew

------Please consider the environment before printing this e-mail.