From: Simon Horman <horms@kernel.org>
To: "Csókás Bence" <csokas.bence@prolan.hu>
Cc: Andrew Lunn <andrew@lunn.ch>, Jakub Kicinski <kuba@kernel.org>,
imx@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Frank Li <Frank.li@nxp.com>,
Wei Fang <wei.fang@nxp.com>, Shenwei Wang <shenwei.wang@nxp.com>,
Clark Wang <xiaoning.wang@nxp.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Richard Cochran <richardcochran@gmail.com>
Subject: Re: [PATCH resubmit net 1/2] net: fec: Forward-declare `fec_ptp_read()`
Date: Thu, 8 Aug 2024 12:37:41 +0100 [thread overview]
Message-ID: <20240808113741.GH3006561@kernel.org> (raw)
In-Reply-To: <449a855a-e3e2-4eed-b8bd-ce64d6f66788@prolan.hu>
On Thu, Aug 08, 2024 at 11:49:29AM +0200, Csókás Bence wrote:
> On 8/8/24 11:41, Simon Horman wrote:
> > 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.
>
> Well, it's not clear to me either what constitutes as a "fix" versus "just a
> cleanup". But, whatever floats Andrew's boat...
Let me state my rule of thumb: a fix addresses a user-visible bug.
> > And if it is a pre-requisite for patch 2/2,
> > well that doesn't seem to be a fix.
>
> It indeed is.
>
> > So in all, I'm somewhat confused.
> > And wonder if all changes can go via net-next.
>
> That's probably what will be happening.
It does seem like the cleanest, and coincidently easiest, path.
next prev parent reply other threads:[~2024-08-08 11:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 8:29 [PATCH resubmit net 1/2] net: fec: Forward-declare `fec_ptp_read()` Csókás, Bence
2024-08-07 8:29 ` [PATCH resubmit net 2/2] net: fec: Remove duplicated code Csókás, Bence
2024-08-07 13:54 ` Andrew Lunn
2024-08-07 14:02 ` Frank Li
2024-08-07 8:35 ` [PATCH resubmit net 1/2] net: fec: Forward-declare `fec_ptp_read()` Csókás Bence
2024-08-07 13:53 ` Andrew Lunn
2024-08-08 9:41 ` Simon Horman
2024-08-08 9:49 ` Csókás Bence
2024-08-08 11:37 ` Simon Horman [this message]
2024-08-08 13:33 ` Andrew Lunn
2024-08-07 14:01 ` Frank Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240808113741.GH3006561@kernel.org \
--to=horms@kernel.org \
--cc=Frank.li@nxp.com \
--cc=andrew@lunn.ch \
--cc=csokas.bence@prolan.hu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=shenwei.wang@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).