From: "Csókás Bence" <csokas.bence@prolan.hu>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Laurent Badel <laurentbadel@eaton.com>,
Andrew Lunn <andrew@lunn.ch>, <imx@lists.linux.dev>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Ahmad Fatoum <a.fatoum@pengutronix.de>,
"Simon Horman" <horms@kernel.org>,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
Jacob Keller <jacob.e.keller@intel.com>,
Wei Fang <wei.fang@nxp.com>, Shenwei Wang <shenwei.wang@nxp.com>,
Clark Wang <xiaoning.wang@nxp.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net v3] net: fec: Refactor MAC reset to function
Date: Wed, 5 Feb 2025 14:53:50 +0100 [thread overview]
Message-ID: <7501c8ee-9272-4c13-91a9-5c614c585fcf@prolan.hu> (raw)
In-Reply-To: <20250204074504.523c794c@kernel.org>
Hi,
On 2025. 02. 04. 16:45, Jakub Kicinski wrote:
> Please don't post new versions in-reply-to, and add lore links to
> the previous version in the changelog.
Will do. Is it okay to only include the last version, or should I
collect them going back to v1?
> On Tue, 4 Feb 2025 10:37:54 +0100 Csókás, Bence wrote:
>> For instance, as of now, `fec_stop()` does not check for
>> `FEC_QUIRK_NO_HARD_RESET`, meaning the MII/RMII mode is cleared on eg.
>> a PM power-down event; and `fec_restart()` missed the refactor renaming
>> the "magic" constant `1` to `FEC_ECR_RESET`.
>
> Laurent responded to v1 saying this was intentional. Please give more
> details on how problem you're seeing and on what platforms. Otherwise
> this is not a fix but refactoring.
True, but he also said:
On 2025. 01. 21. 17:09, Badel, Laurent wrote:
> If others disagree and there's a consensus that this change is ok,
I'm happy
> for the patch to get through, but I tend to err on the side of
caution in such
> cases.
I understand he is cautious, but I'd argue that the fact that two people
already posted Reviewed-by: (not counting Simon, who since withdrew it),
means that others also agree that we should err on the OTHER side of
caution, and do the check in both cases. He also mentions that the
reason he didn't do the check in `fec_stop()` was that he believed that
the only time that gets called is on driver/interface remove, but that
is not the case, as I outlined in the message already.
Bence
next prev parent reply other threads:[~2025-02-05 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 16:39 [PATCH] net: fec: Refactor MAC reset to function Csókás, Bence
2025-01-22 19:47 ` Jacob Keller
2025-01-23 1:24 ` Wei Fang
2025-02-04 9:37 ` [PATCH net v3] " Csókás, Bence
2025-02-04 15:45 ` Jakub Kicinski
2025-02-05 13:53 ` Csókás Bence [this message]
2025-02-06 1:06 ` Jakub Kicinski
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=7501c8ee-9272-4c13-91a9-5c614c585fcf@prolan.hu \
--to=csokas.bence@prolan.hu \
--cc=a.fatoum@pengutronix.de \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=imx@lists.linux.dev \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=laurentbadel@eaton.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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