[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220118130015.3118e0de@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
Date: Tue, 18 Jan 2022 13:00:15 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Robert Hancock <robert.hancock@...ian.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"andrew@...n.ch" <andrew@...n.ch>,
"daniel@...earbox.net" <daniel@...earbox.net>,
"radhey.shyam.pandey@...inx.com" <radhey.shyam.pandey@...inx.com>,
"michal.simek@...inx.com" <michal.simek@...inx.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"ariane.keller@....ee.ethz.ch" <ariane.keller@....ee.ethz.ch>
Subject: Re: [PATCH net v2 0/9] Xilinx axienet fixes
On Tue, 18 Jan 2022 20:45:31 +0000 Robert Hancock wrote:
> On Wed, 2022-01-12 at 11:36 -0600, Robert Hancock wrote:
> > Various fixes for the Xilinx AXI Ethernet driver.
> >
> > Changed since v1:
> > -corrected a Fixes tag to point to mainline commit
> > -split up reset changes into 3 patches
> > -added ratelimit on netdev_warn in TX busy case
> >
> > Robert Hancock (9):
> > net: axienet: increase reset timeout
> > net: axienet: Wait for PhyRstCmplt after core reset
> > net: axienet: reset core on initialization prior to MDIO access
> > net: axienet: add missing memory barriers
> > net: axienet: limit minimum TX ring size
> > net: axienet: Fix TX ring slot available check
> > net: axienet: fix number of TX ring slots for available check
> > net: axienet: fix for TX busy handling
> > net: axienet: increase default TX ring size to 128
>
> Any other comments/reviews on this patch set? It's marked as Changes Requested
> in Patchwork, but I don't think I saw any discussions that ended up with any
> changes being asked for?
Perhaps it was done in anticipation to follow up to Radhey's or
Andrew's question but seems like you answered those. Or maybe because
of the missing CC on of hancock@...systems.ca on patch 5?
Not sure.
Could you fold some of the explanations into commit messages, add
Andrew's Acks and post a v3?
We could probably apply as is but since it was marked as Changes
Requested I can't be sure someone hasn't stopped reviewing in
anticipation of v3.
Thanks!
Powered by blists - more mailing lists