From: Wei Fang <wei.fang@nxp.com>
To: Bui Duc Phuc <phucduc.bui@gmail.com>
Cc: 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 01:52:33 +0000 [thread overview]
Message-ID: <GV2PR04MB1173931CA07AEAB48339FF71588B52@GV2PR04MB11739.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CAABR9nFD1+GJiWdyxiuGVRzKjpCUfu3TQHYOLnOym3hHzOM2tg@mail.gmail.com>
> > > Fixes: b86bcb299092 ("net: fec_ptp: Use platform_get_irq_xxx_optional() to
> > > avoid error message")
> >
> > If this is a bug fix, it should target to net tree rather than net-next.
> >
>
>
> On a previous (different) patch with a Fixes tag, I was advised to
> target 'net-next' instead,
> so I submitted this one to 'net-next' first to be safe.
>
> If you think this fix for commit b86bcb299092 belongs in 'net', please
> let me know and
> I will resubmit it as a v2 targeting the 'net' tree.
>
Is this a real bug that bothers people? or just an improvement?
For real bug, I think the patch should target to net tree.
next prev parent reply other threads:[~2026-09-04 1:52 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 [this message]
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
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=GV2PR04MB1173931CA07AEAB48339FF71588B52@GV2PR04MB11739.eurprd04.prod.outlook.com \
--to=wei.fang@nxp.com \
--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 \
/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