[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191008160222.0bdb7f47@cakuba.netronome.com>
Date: Tue, 8 Oct 2019 16:02:22 -0700
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: MarkLee <Mark-MC.Lee@...iatek.com>
Cc: "David S. Miller" <davem@...emloft.net>,
Sean Wang <sean.wang@...iatek.com>,
John Crispin <john@...ozen.org>,
Nelson Chang <nelson.chang@...iatek.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Andrew Lunn <andrew@...n.ch>, Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Rene van Dorst <opensource@...rst.com>,
<devicetree@...r.kernel.org>, <netdev@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net,v2 0/2] Update MT7629 to support PHYLINK API
On Mon, 7 Oct 2019 15:08:42 +0800, MarkLee wrote:
> This patch target to update mt7629 eth driver and dts to support PHYLINK
Thanks for the patches Mark. The description of the set should probably
say that it _fixes_ some issues. Right now it sounds a little bit like
you were adding a new feature. Could you rewrite the cover letter to
give us a better idea what issues this patch set is fixing and why
those issues occur?
Powered by blists - more mailing lists