netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Parthiban.Veerasooran@microchip.com>
To: <Horatiu.Vultur@microchip.com>
Cc: <andrew@lunn.ch>, <hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
	<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
	<pabeni@redhat.com>, <ramon.nordin.rodriguez@ferroamp.se>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<UNGLinuxDriver@microchip.com>,
	<Thorsten.Kummermehr@microchip.com>
Subject: Re: [PATCH net-next v2 0/7] microchip_t1s: Update on Microchip 10BASE-T1S PHY driver
Date: Wed, 4 Sep 2024 11:28:34 +0000	[thread overview]
Message-ID: <a0428bdb-d422-4801-ab1e-649c409bc03e@microchip.com> (raw)
In-Reply-To: <20240903062441.otbn6qcrhjisovhy@DEN-DL-M31836.microchip.com>

Hi Horatiu,

On 03/09/24 11:54 am, Horatiu Vultur wrote:
> The 09/02/2024 20:04, Parthiban Veerasooran wrote:
> 
> Hi Parthiban,
> 
>> This patch series contain the below updates,
>>
>> v1:
> 
> You usually use v1, v2, v3 to say what is the difference between series.
> But in your case you already had v1 already in first patch series which
> it is strange to be used. I think you wanted to just describe the
> features of this patch series.
> So, my suggestion is to drop v1 because those are the features not
> changes between version, and put ':' instead of ',' after updates.
Ah yes, will correct them in the next version.
> 
> Also almost all your patches in this series start with 'This patch',
> please change this to imperative mode:
> https://www.kernel.org/doc/html/v4.10/process/submitting-patches.html
OK. Will correct them in the next version.

Best regards,
Parthiban V
> 
>> - Restructured lan865x_write_cfg_params() and lan865x_read_cfg_params()
>>    functions arguments to more generic.
>> - Updated new/improved initial settings of LAN865X Rev.B0 from latest
>>    AN1760.
>> - Added support for LAN865X Rev.B1 from latest AN1760.
>> - Moved LAN867X reset handling to a new function for flexibility.
>> - Added support for LAN867X Rev.C1/C2 from latest AN1699.
>> - Disabled/enabled collision detection based on PLCA setting.
>>
>> v2:
>> - Fixed indexing issue in the configuration parameter setup.
>>
>> Parthiban Veerasooran (7):
>>    net: phy: microchip_t1s: restructure cfg read/write functions
>>      arguments
>>    net: phy: microchip_t1s: update new initial settings for LAN865X
>>      Rev.B0
>>    net: phy: microchip_t1s: add support for Microchip's LAN865X Rev.B1
>>    net: phy: microchip_t1s: move LAN867X reset handling to a new function
>>    net: phy: microchip_t1s: add support for Microchip's LAN867X Rev.C1
>>    net: phy: microchip_t1s: add support for Microchip's LAN867X Rev.C2
>>    net: phy: microchip_t1s: configure collision detection based on PLCA
>>      mode
>>
>>   drivers/net/phy/Kconfig         |   4 +-
>>   drivers/net/phy/microchip_t1s.c | 299 +++++++++++++++++++++++++-------
>>   2 files changed, 239 insertions(+), 64 deletions(-)
>>
>>
>> base-commit: 221f9cce949ac8042f65b71ed1fde13b99073256
>> -- 
>> 2.34.1
>>
> 


      reply	other threads:[~2024-09-04 11:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02 14:34 [PATCH net-next v2 0/7] microchip_t1s: Update on Microchip 10BASE-T1S PHY driver Parthiban Veerasooran
2024-09-02 14:34 ` [PATCH net-next v2 1/7] net: phy: microchip_t1s: restructure cfg read/write functions arguments Parthiban Veerasooran
2024-09-02 14:34 ` [PATCH net-next v2 2/7] net: phy: microchip_t1s: update new initial settings for LAN865X Rev.B0 Parthiban Veerasooran
2024-09-03  6:33   ` Horatiu Vultur
2024-09-04 10:20     ` Parthiban.Veerasooran
2024-09-06  6:37       ` Horatiu Vultur - M31836
2024-09-09  8:36         ` Parthiban.Veerasooran
2024-09-02 14:34 ` [PATCH net-next v2 3/7] net: phy: microchip_t1s: add support for Microchip's LAN865X Rev.B1 Parthiban Veerasooran
2024-09-03  6:36   ` Horatiu Vultur
2024-09-04 10:30     ` Parthiban.Veerasooran
2024-09-02 14:34 ` [PATCH net-next v2 4/7] net: phy: microchip_t1s: move LAN867X reset handling to a new function Parthiban Veerasooran
2024-09-02 14:34 ` [PATCH net-next v2 5/7] net: phy: microchip_t1s: add support for Microchip's LAN867X Rev.C1 Parthiban Veerasooran
2024-09-03  7:30   ` Simon Horman
2024-09-04 11:25     ` Parthiban.Veerasooran
2024-09-02 14:34 ` [PATCH net-next v2 6/7] net: phy: microchip_t1s: add support for Microchip's LAN867X Rev.C2 Parthiban Veerasooran
2024-09-02 14:34 ` [PATCH net-next v2 7/7] net: phy: microchip_t1s: configure collision detection based on PLCA mode Parthiban Veerasooran
2024-09-03  6:43   ` Horatiu Vultur
2024-09-04 11:46     ` Parthiban.Veerasooran
2024-09-06  6:43       ` Horatiu Vultur - M31836
2024-09-09  9:30         ` Parthiban.Veerasooran
2024-09-03  6:24 ` [PATCH net-next v2 0/7] microchip_t1s: Update on Microchip 10BASE-T1S PHY driver Horatiu Vultur
2024-09-04 11:28   ` Parthiban.Veerasooran [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=a0428bdb-d422-4801-ab1e-649c409bc03e@microchip.com \
    --to=parthiban.veerasooran@microchip.com \
    --cc=Horatiu.Vultur@microchip.com \
    --cc=Thorsten.Kummermehr@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ramon.nordin.rodriguez@ferroamp.se \
    /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).