From: Andrew Lunn <andrew@lunn.ch>
To: Kyle Switch <kyle.switch@motor-comm.com>
Cc: Frank.Sae@motor-comm.com, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, ming.xu@motor-comm.com,
xiaolin.xu@motor-comm.com, jianmin.wang@motor-comm.com,
jie.han@motor-comm.com
Subject: Re: [Patch net-next v3] net: phy: Add driver for Motorcomm Quad 2.5GbE phy
Date: Mon, 20 Jul 2026 15:37:35 +0200 [thread overview]
Message-ID: <f3b70dc6-95ff-4add-8b1d-6534fe4dc3f6@lunn.ch> (raw)
In-Reply-To: <3d87f3d1-83c6-49b5-ac6f-59880c6a6c6c@motor-comm.com>
> >> -static struct phy_driver motorcomm_phy_drvs[] = {
> >> - {
> >> - PHY_ID_MATCH_EXACT(PHY_ID_YT8511),
> >> - .name = "YT8511 Gigabit Ethernet",
> >> - .config_init = yt8511_config_init,
> >> - .suspend = genphy_suspend,
> >> - .resume = genphy_resume,
> >> - .read_page = yt8511_read_page,
> >> - .write_page = yt8511_write_page,
> >> - },
> >
> > I still don't like this. Please stop diff deleting all these and
> > putting them back later. It makes me thing something changed, maybe
> > white space?
>
> Ans: I tried to refactor this issue by hanging the position of the newly
> added code. However, the same issue may still arise in other code segments,
> without modifying the existing code.
Look at other patches on this list. Look at the diff generated. Do you
see the same sort of issue? I'm pretty sure something is wrong here.
Try
git reset HEAD~1
git diff -w
and see if you get a different diff. That would indicate there is a
whitespace change you need to revert.
Andrew
next prev parent reply other threads:[~2026-07-20 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 5:48 [Patch net-next v3] net: phy: Add driver for Motorcomm Quad 2.5GbE phy Kyle Switch
2026-07-17 14:53 ` Andrew Lunn
2026-07-20 8:47 ` Kyle Switch
2026-07-17 15:11 ` Andrew Lunn
2026-07-20 9:05 ` Kyle Switch
2026-07-20 13:37 ` Andrew Lunn [this message]
2026-07-17 20:19 ` Krzysztof Kozlowski
2026-07-20 8:45 ` Kyle Switch
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=f3b70dc6-95ff-4add-8b1d-6534fe4dc3f6@lunn.ch \
--to=andrew@lunn.ch \
--cc=Frank.Sae@motor-comm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=jianmin.wang@motor-comm.com \
--cc=jie.han@motor-comm.com \
--cc=kuba@kernel.org \
--cc=kyle.switch@motor-comm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ming.xu@motor-comm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xiaolin.xu@motor-comm.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