From: Andrew Lunn <andrew@lunn.ch>
To: Bui Duc Phuc <phucduc.bui@gmail.com>
Cc: Wei Fang <wei.fang@nxp.com>, Frank Li <frank.li@nxp.com>,
Shenwei Wang <shenwei.wang@nxp.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"davem@davemloft.net" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Richard Cochran <richardcochran@gmail.com>,
Anson Huang <Anson.Huang@nxp.com>,
Stephen Boyd <swboyd@chromium.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v2] net: fec: Propagate PTP initialization errors
Date: Fri, 4 Sep 2026 14:45:32 +0200 [thread overview]
Message-ID: <d12608a5-468a-44ca-9442-07f2eee4e335@lunn.ch> (raw)
In-Reply-To: <CAABR9nFi06-7=uHmOBFGZv1eUYCskv8WspOdUxbDuQ6vMk68Dg@mail.gmail.com>
> Second, the current implementation can silently ignore -EPROBE_DEFER and
> continue probing instead of deferring.
This is a stronger reason. You should mention it in the commit message
as part of your justification for net, rather than net-next.
Andrew
next prev parent reply other threads:[~2026-09-04 12:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 9:24 [PATCH net-next v2] net: fec: Propagate PTP initialization errors phucduc.bui
2026-09-03 9:29 ` Wei Fang
2026-09-03 10:45 ` Bui Duc Phuc
2026-09-04 1:52 ` Wei Fang
2026-09-04 3:03 ` Bui Duc Phuc
2026-09-04 3:23 ` Wei Fang
2026-09-04 9:16 ` Bui Duc Phuc
2026-09-04 12:45 ` Andrew Lunn [this message]
2026-09-03 14:37 ` Andrew Lunn
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=d12608a5-468a-44ca-9442-07f2eee4e335@lunn.ch \
--to=andrew@lunn.ch \
--cc=Anson.Huang@nxp.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=frank.li@nxp.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=phucduc.bui@gmail.com \
--cc=richardcochran@gmail.com \
--cc=shenwei.wang@nxp.com \
--cc=swboyd@chromium.org \
--cc=wei.fang@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