netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: "SkyLake Huang (黃啟澤)" <SkyLake.Huang@mediatek.com>
Cc: "andrew@lunn.ch" <andrew@lunn.ch>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"edumazet@google.com" <edumazet@google.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"dqfext@gmail.com" <dqfext@gmail.com>,
	"Steven Liu (劉人豪)" <steven.liu@mediatek.com>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
	"daniel@makrotopia.org" <daniel@makrotopia.org>,
	"angelogioacchino.delregno@collabora.com"
	<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH net-next v7 5/5] net: phy: add driver for built-in 2.5G ethernet PHY on MT7988
Date: Wed, 19 Jun 2024 21:09:50 +0100	[thread overview]
Message-ID: <ZnM7DkKhMABNgjEi@shell.armlinux.org.uk> (raw)
In-Reply-To: <ac5cfcdeefb350af4467fe163b8a93b7873d3889.camel@mediatek.com>

On Wed, Jun 19, 2024 at 11:44:32AM +0000, SkyLake Huang (黃啟澤) wrote:
> On Wed, 2024-06-19 at 10:09 +0100, Russell King (Oracle) wrote:
> >  	 
> > External email : Please do not click links or open attachments until
> > you have verified the sender or the content.
> >  On Thu, Jun 13, 2024 at 06:40:23PM +0800, Sky Huang wrote:
> > > +static struct phy_driver mtk_gephy_driver[] = {
> > > +{
> > > +PHY_ID_MATCH_MODEL(MTK_2P5GPHY_ID_MT7988),
> > > +.name= "MediaTek MT7988 2.5GbE PHY",
> > > +.probe= mt798x_2p5ge_phy_probe,
> > > +.config_init= mt798x_2p5ge_phy_config_init,
> > > +.config_aneg    = mt798x_2p5ge_phy_config_aneg,
> > > +.get_features= mt798x_2p5ge_phy_get_features,
> > > +.read_status= mt798x_2p5ge_phy_read_status,
> > > +.get_rate_matching= mt798x_2p5ge_phy_get_rate_matching,
> > > +.suspend= genphy_suspend,
> > > +.resume= genphy_resume,
> > > +.read_page= mtk_phy_read_page,
> > > +.write_page= mtk_phy_write_page,
> > > +.led_blink_set= mt798x_2p5ge_phy_led_blink_set,
> > > +.led_brightness_set = mt798x_2p5ge_phy_led_brightness_set,
> > > +.led_hw_is_supported = mt798x_2p5ge_phy_led_hw_is_supported,
> > > +.led_hw_control_get = mt798x_2p5ge_phy_led_hw_control_get,
> > > +.led_hw_control_set = mt798x_2p5ge_phy_led_hw_control_set,
> > 
> > I don't see the point of trying to align some of these method
> > declarators but not others. Consistency is important.
> > 
> Sorry I don't get your point on this. What do you mean by "trying to
> align some of these method declarators but not others"? Do you mean
> "mt798x_2p5ge_phy" prefix?

Some of the method initialisers are:

	.foo<tab>= method_foo,
	.bar<tab>= method_bar,
	...

while other are:

	.longlongname<space>= methodlonglongname,

So what this causes is:

	.foo	= method_foo,
	.bar	= method_bar,
	.longlongbaz = methodlonglongbaz,

which looks messy - why use tabs for the short ones and a space for
the others. Why not be consistent, e.g.:

	.foo = method_foo,
	.bar = method_bar,
	.longlongbaz = methodlonglongbaz,

?

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2024-06-19 20:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 10:40 [PATCH net-next v7 0/5] net: phy: mediatek: Introduce mtk-phy-lib and add 2.5Gphy support Sky Huang
2024-06-13 10:40 ` [PATCH net-next v7 1/5] net: phy: mediatek: Re-organize MediaTek ethernet phy drivers Sky Huang
2024-06-19  8:31   ` Russell King (Oracle)
2024-06-19  9:14     ` SkyLake Huang (黃啟澤)
2024-06-13 10:40 ` [PATCH net-next v7 2/5] net: phy: mediatek: Move LED and read/write page helper functions into mtk phy lib Sky Huang
2024-06-17 11:51   ` Simon Horman
2024-06-19  8:13     ` SkyLake Huang (黃啟澤)
2024-06-18 15:21   ` Jakub Kicinski
2024-06-19  8:17     ` SkyLake Huang (黃啟澤)
2024-06-19 10:37       ` SkyLake Huang (黃啟澤)
2024-06-19  8:58   ` Russell King (Oracle)
2024-06-19 11:21     ` SkyLake Huang (黃啟澤)
2024-06-13 10:40 ` [PATCH net-next v7 3/5] net: phy: mediatek: Add token ring access helper functions in mtk-phy-lib Sky Huang
2024-06-19  9:01   ` Russell King (Oracle)
2024-06-19 11:33     ` SkyLake Huang (黃啟澤)
2024-06-13 10:40 ` [PATCH net-next v7 4/5] net: phy: mediatek: Extend 1G TX/RX link pulse time Sky Huang
2024-06-13 10:40 ` [PATCH net-next v7 5/5] net: phy: add driver for built-in 2.5G ethernet PHY on MT7988 Sky Huang
2024-06-19  9:09   ` Russell King (Oracle)
2024-06-19 11:44     ` SkyLake Huang (黃啟澤)
2024-06-19 20:09       ` Russell King (Oracle) [this message]
2024-06-20  4:32         ` SkyLake Huang (黃啟澤)

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=ZnM7DkKhMABNgjEi@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=SkyLake.Huang@mediatek.com \
    --cc=andrew@lunn.ch \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=daniel@makrotopia.org \
    --cc=davem@davemloft.net \
    --cc=dqfext@gmail.com \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=steven.liu@mediatek.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;
as well as URLs for NNTP newsgroup(s).