public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <Rakesh.Sankaranarayanan@microchip.com>
To: <olteanv@gmail.com>, <andrew@lunn.ch>
Cc: <davem@davemloft.net>, <pabeni@redhat.com>,
	<hkallweit1@gmail.com>, <Arun.Ramadoss@microchip.com>,
	<Woojung.Huh@microchip.com>, <linux-kernel@vger.kernel.org>,
	<linux@armlinux.org.uk>, <f.fainelli@gmail.com>,
	<kuba@kernel.org>, <edumazet@google.com>,
	<UNGLinuxDriver@microchip.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH net 2/2] net: dsa: microchip: lan937x: run phy initialization during each link update
Date: Thu, 19 Jan 2023 11:34:00 +0000	[thread overview]
Message-ID: <7d72bc330d0ce9e57cc862bec39388b7def8782a.camel@microchip.com> (raw)
In-Reply-To: <20230116222602.oswnt4ecoucpb2km@skbuf>

Hi Vladimir,
Thanks for the comments.

> 1. Don't prefix a patch with "net: dsa: microchip: " unless it
> touches
>    the drivers/net/dsa/microchip/ folder.
> 
> 2. Don't make unrelated patches on different drivers part of the same
>    patch set.
> 
I will update the patch in next revision.

> 3. AFAIU, this is the second fixup of a feature which never worked
> well
>    (changing master/slave setting through ethtool). Not sure exactly
>    what are the rules, but at some point, maintainers might say
>    "hey, let go, this never worked, just send your fixes to net-
> next".
>    I mean: (1) fixes of fixes of smth that never worked can't be sent
> ad
>    infinitum, especially if not small and (2) there needs to be some
>    incentive to submit code that actually works and was tested,
> rather
>    than a placeholder which can be fixed up later, right? In this
> case,
>    I'm not sure, this seems borderline net-next. Let's see what the
> PHY
>    library maintainers think.
> 

Thanks for pointing this out. Do you think submitting this patch in
net-next is the right way?

@andrew,
Do you have any thoughts on this?

Thanks,
Rakesh S.

  reply	other threads:[~2023-01-19 11:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16 10:04 [PATCH net 0/2] phy init update and alu table correction Rakesh Sankaranarayanan
2023-01-16 10:04 ` [PATCH net 1/2] net: dsa: microchip: ksz9477: port map correction in ALU table entry register Rakesh Sankaranarayanan
2023-01-16 20:59   ` Vladimir Oltean
2023-01-16 10:05 ` [PATCH net 2/2] net: dsa: microchip: lan937x: run phy initialization during each link update Rakesh Sankaranarayanan
2023-01-16 22:26   ` Vladimir Oltean
2023-01-19 11:34     ` Rakesh.Sankaranarayanan [this message]
2023-01-19 11:36       ` Vladimir Oltean
2023-01-19 17:27       ` Andrew Lunn
2023-01-19 17:35         ` Jakub Kicinski
2023-01-20 10:19           ` Rakesh.Sankaranarayanan

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=7d72bc330d0ce9e57cc862bec39388b7def8782a.camel@microchip.com \
    --to=rakesh.sankaranarayanan@microchip.com \
    --cc=Arun.Ramadoss@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=Woojung.Huh@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.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=olteanv@gmail.com \
    --cc=pabeni@redhat.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