From: Francesco Dolcini <francesco.dolcini@toradex.com>
To: "Csókás Bence" <csokas.bence@prolan.hu>
Cc: Joakim Zhang <qiangqing.zhang@nxp.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Marc Kleine-Budde <mkl@pengutronix.de>,
Guenter Roeck <linux@roeck-us.net>, Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH net 0/2] Revert fec PTP changes
Date: Mon, 12 Sep 2022 09:07:23 +0200 [thread overview]
Message-ID: <20220912070723.GA98330@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <20220912070143.98153-1-francesco.dolcini@toradex.com>
On Mon, Sep 12, 2022 at 09:01:41AM +0200, Francesco Dolcini wrote:
> Revert the last 2 FEC PTP changes from Csókás Bence, they are causing multiple
> issues and we are at 6.0-rc5.
Hello Csókás,
the net maintainers will decide how to proceed on this, IMO now we
should just revert both. In parallel you can work on a new patch to
handle the PTP issue you were trying to address.
BR,
Francesco
next prev parent reply other threads:[~2022-09-12 7:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 7:01 Francesco Dolcini
2022-09-12 7:01 ` [PATCH net 1/2] Revert "fec: Restart PPS after link state change" Francesco Dolcini
2022-09-12 12:07 ` Andrew Lunn
2022-09-12 12:32 ` Marc Kleine-Budde
2022-09-12 7:01 ` [PATCH net 2/2] Revert "net: fec: Use a spinlock to guard `fep->ptp_clk_on`" Francesco Dolcini
2022-09-12 12:05 ` Andrew Lunn
2022-09-12 12:32 ` Marc Kleine-Budde
2022-09-12 7:07 ` Francesco Dolcini [this message]
2022-09-12 12:28 ` [PATCH net 0/2] Revert fec PTP changes Marc Kleine-Budde
2022-09-12 12:38 ` Francesco Dolcini
2022-09-20 7:45 ` Thorsten Leemhuis
2022-09-20 9:51 ` Paolo Abeni
2022-09-20 10:30 ` patchwork-bot+netdevbpf
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=20220912070723.GA98330@francesco-nb.int.toradex.com \
--to=francesco.dolcini@toradex.com \
--cc=andrew@lunn.ch \
--cc=csokas.bence@prolan.hu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qiangqing.zhang@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
all inboxes | Powered by JetHome®