The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Selvamani Rajagopal <Selvamani.Rajagopal@onsemi.com>
Cc: Piergiorgio Beruto <Pier.Beruto@onsemi.com>,
	"parthiban.veerasooran@microchip.com"
	<parthiban.veerasooran@microchip.com>,
	"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v2 7/9] net: ethernet: oa_tc6: fix for minor issues
Date: Mon, 11 May 2026 21:55:22 +0200	[thread overview]
Message-ID: <587f96bb-bcfd-4515-a4b6-e9e4292ce5a1@lunn.ch> (raw)
In-Reply-To: <CY8PR02MB92494EEBB98152678D3CCEF183382@CY8PR02MB9249.namprd02.prod.outlook.com>

> @@ -459,9 +459,7 @@ EXPORT_SYMBOL_GPL(oa_tc6_hwtstamp_ioctl);
>  /**
>   * Add vendor specific MDIO_MMD to OA TC6 MMS mapper value.
>   * @tc6: oa_tc6 struct.
> - * @mms: vendor defined MMS value.
> - *
> - * Return: 0 on success otherwise failed.
> + * @mms: vendor defined MMS value for VEND1 mdio device.

You just added this in a previous patch. Don't patch your own patch,
get it right the first time.

> @@ -701,7 +699,7 @@ static int oa_tc6_mdiobus_read(struct mii_bus *bus, int addr, int regnum)
>  {
>  	struct oa_tc6 *tc6 = bus->priv;
>  	u32 regval;
> -	bool ret;
> +	int ret;
>  
>  	ret = oa_tc6_read_register(tc6, OA_TC6_PHY_STD_REG_ADDR_BASE |
>  				   (regnum & OA_TC6_PHY_STD_REG_ADDR_MASK),
> @@ -864,7 +862,7 @@ static void oa_tc6_phy_exit(struct oa_tc6 *tc6)
>  	oa_tc6_mdiobus_unregister(tc6);
>  }

Please put this in a patch of its own, with a good commit
message. Lots of small patches, each with a good commit message.


>  
> -static int oa_tc6_read_status0(struct oa_tc6 *tc6)
> +static u32 oa_tc6_read_status0(struct oa_tc6 *tc6)
>  {
>  	u32 regval;
>  	int ret;

A patch of its own, and the commit message can explain why, because it
takes a bit of work to understand why.

	Andrew

      reply	other threads:[~2026-05-11 19:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 18:19 [PATCH net-next v2 7/9] net: ethernet: oa_tc6: fix for minor issues Selvamani Rajagopal
2026-05-11 19:55 ` 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=587f96bb-bcfd-4515-a4b6-e9e4292ce5a1@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Pier.Beruto@onsemi.com \
    --cc=Selvamani.Rajagopal@onsemi.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=parthiban.veerasooran@microchip.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