[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <433ffa6c-7ad3-4e28-a2ef-de699bf0e03a@lunn.ch>
Date: Sun, 19 May 2024 17:37:39 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Matthew Wilcox <willy@...radead.org>
Cc: Markus Elfring <Markus.Elfring@....de>,
Siddharth Vadapalli <s-vadapalli@...com>, netdev@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
kernel-janitors@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Jonathan Corbet <corbet@....net>,
MD Danish Anwar <danishanwar@...com>,
Paolo Abeni <pabeni@...hat.com>, Roger Quadros <rogerq@...nel.org>,
Vladimir Oltean <vladimir.oltean@....com>,
LKML <linux-kernel@...r.kernel.org>, linux-doc@...r.kernel.org,
Misael Lopez Cruz <misael.lopez@...com>,
Sriramakrishnan <srk@...com>, Vignesh Raghavendra <vigneshr@...com>
Subject: Re: [RFC PATCH net-next 12/28] net: ethernet: ti: cpsw-proxy-client:
add NAPI RX polling function
On Sun, May 19, 2024 at 03:00:42PM +0100, Matthew Wilcox wrote:
>
> FYI, Markus can be safely ignored. His opinions are well-established as
> being irrelevant.
I personally would suggest ignoring the nit-gritty details for the
moment, and concentrate on the big picture architecture. I suspect the
basic architecture is wrong, and the code is going to change in big
ways. So it is pointless reviewing the code at the moment, other than
to understand the architecture.
Andrew
Powered by blists - more mailing lists