[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240808094116.GG3006561@kernel.org>
Date: Thu, 8 Aug 2024 10:41:16 +0100
From: Simon Horman <horms@...nel.org>
To: Andrew Lunn <andrew@...n.ch>
Cc: Csókás, Bence <csokas.bence@...lan.hu>,
Jakub Kicinski <kuba@...nel.org>, imx@...ts.linux.dev,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Frank Li <Frank.li@....com>, Wei Fang <wei.fang@....com>,
Shenwei Wang <shenwei.wang@....com>,
Clark Wang <xiaoning.wang@....com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
Richard Cochran <richardcochran@...il.com>
Subject: Re: [PATCH resubmit net 1/2] net: fec: Forward-declare
`fec_ptp_read()`
On Wed, Aug 07, 2024 at 03:53:17PM +0200, Andrew Lunn wrote:
> On Wed, Aug 07, 2024 at 10:29:17AM +0200, Csókás, Bence wrote:
> > This function is used in `fec_ptp_enable_pps()` through
> > struct cyclecounter read(). Forward declarations make
> > it clearer, what's happening.
>
> In general, forward declarations are not liked. It is better to move
> the code to before it is used.
>
> Since this is a minimal fix for stable, lets allow it. But please wait
> for net to be merged into net-next, and submit a cleanup patch which
> does move fec_ptp_read() earlier and remove the forward declaration.
That makes sense.
However, is this a fix?
It's not clear to me that it is.
And if it is a pre-requisite for patch 2/2,
well that doesn't seem to be a fix.
So in all, I'm somewhat confused.
And wonder if all changes can go via net-next.
Powered by blists - more mailing lists