netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Maxim Kochetkov <fido_max@inbox.ru>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com,
	hkallweit1@gmail.com
Subject: Re: [PATCH v2 01/02] net: phy: marvell: Add Marvell 88E1340 support
Date: Wed, 17 Jun 2020 09:47:29 +0100	[thread overview]
Message-ID: <20200617084729.GN1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <05f6912b-d529-ae7d-183e-efa6951e94b7@inbox.ru>

On Wed, Jun 17, 2020 at 07:52:45AM +0300, Maxim Kochetkov wrote:
> Add Marvell 88E1340 support
> Signed-off-by: Maxim Kochetkov <fido_max@inbox.ru>
> ---
>  drivers/net/phy/marvell.c   | 23 +++++++++++++++++++++++
>  include/linux/marvell_phy.h |  1 +
>  2 files changed, 24 insertions(+)
> 
> diff --git a/drivers/net/phy/marvell.c b/drivers/net/phy/marvell.c
> index 7fc8e10c5f33..4cc4e25fed2d 100644
> --- a/drivers/net/phy/marvell.c
> +++ b/drivers/net/phy/marvell.c
> @@ -2459,6 +2459,28 @@ static struct phy_driver marvell_drivers[] = {
>  		.get_tunable = m88e1540_get_tunable,
>  		.set_tunable = m88e1540_set_tunable,
>  	},
> +	{
> +		.phy_id = MARVELL_PHY_ID_88E1340S,
> +		.phy_id_mask = MARVELL_PHY_ID_MASK,
> +		.name = "Marvell 88E1340S",
> +		.probe = m88e1510_probe,
> +		/* PHY_GBIT_FEATURES */
> +		.config_init = &marvell_config_init,
> +		.config_aneg = &m88e1510_config_aneg,
> +		.read_status = &marvell_read_status,
> +		.ack_interrupt = &marvell_ack_interrupt,
> +		.config_intr = &marvell_config_intr,
> +		.did_interrupt = &m88e1121_did_interrupt,
> +		.resume = &genphy_resume,
> +		.suspend = &genphy_suspend,
> +		.read_page = marvell_read_page,
> +		.write_page = marvell_write_page,
> +		.get_sset_count = marvell_get_sset_count,
> +		.get_strings = marvell_get_strings,
> +		.get_stats = marvell_get_stats,
> +		.get_tunable = m88e1540_get_tunable,
> +		.set_tunable = m88e1540_set_tunable,

Can we use a single style for referencing functions please?  The kernel
in general does not use &func, it's more typing than is necessary.  The
C99 standard says:

   6.3.2.1  Lvalues, arrays, and function designators

4  A function designator is an expression that has function type.
   Except when it is the operand of the sizeof operator or the unary
   & operator, a function designator with type ``function returning
   type'' is converted to an expression that has type ``pointer to
   function returning type''.

Hence, 

  .resume = &genphy_resume

and

  .resume = genphy_resume

are equivalent but sizeof(genphy_resume) and sizeof(&genphy_resume) are
not.

Thanks.

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

  reply	other threads:[~2020-06-17  8:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17  4:52 [PATCH v2 01/02] net: phy: marvell: Add Marvell 88E1340 support Maxim Kochetkov
2020-06-17  8:47 ` Russell King - ARM Linux admin [this message]
2020-06-17  9:59   ` Maxim Kochetkov
2020-06-19  3:24 ` David Miller

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=20200617084729.GN1551@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --cc=fido_max@inbox.ru \
    --cc=hkallweit1@gmail.com \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).