From: Andrew Lunn <andrew@lunn.ch>
To: Yongzhao Chen <yongzhao.derek@gmail.com>
Cc: Christian Marangi <ansuelsmth@gmail.com>,
netdev@vger.kernel.org, Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: phy: qca83xx: read resolved QCA8337 link status
Date: Sat, 3 Oct 2026 16:38:06 +0200 [thread overview]
Message-ID: <36c4c389-bc11-4363-8e23-eb8199dc3499@lunn.ch> (raw)
In-Reply-To: <20261002203522.1219-1-yongzhao.derek@gmail.com>
On Fri, Oct 02, 2026 at 10:35:22PM +0200, Yongzhao Chen wrote:
> Hi Andrew,
>
> > The traffic failure was however because of the error with setting the
> > DACs?
>
> No, sorry, my last mail was not clear about this. The failure was on
> a QCA8337 user port connected to a NAS
In that case, net. It is a real problem that bothers somebody,
you. That fulfils the requirements for stable.
With LLM, we see a lot of patches fixing issues which nobody ever
comes across, they are theoretical. We want those to go into net-next.
So ideally we want to clear indication in the commit message that the
fix is for a real problem. There is now an automated email when
patches are submitted when it is not clear if they are theoretical or
real fixes, reproduced on real hardware, or just build tested, etc.
Andrew
prev parent reply other threads:[~2026-10-03 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 22:07 [PATCH net-next] net: phy: qca83xx: read resolved QCA8337 link status Yongzhao Chen
2026-09-29 0:40 ` Andrew Lunn
2026-09-30 21:23 ` Yongzhao Chen
2026-09-30 21:33 ` Andrew Lunn
2026-10-01 18:16 ` Yongzhao Chen
2026-10-01 18:46 ` Andrew Lunn
2026-10-02 20:35 ` Yongzhao Chen
2026-10-03 14:38 ` Andrew Lunn [this message]
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=36c4c389-bc11-4363-8e23-eb8199dc3499@lunn.ch \
--to=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yongzhao.derek@gmail.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