[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <70234187-3e7d-4932-8b07-42973337ecb1@lunn.ch>
Date: Mon, 22 May 2023 16:42:02 +0200
From: Andrew Lunn <andrew@...n.ch>
To: David Epping <david.epping@...singlinkelectronics.com>
Cc: Vladimir Oltean <olteanv@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
UNGLinuxDriver@...rochip.com
Subject: Re: [PATCH net 3/3] net: phy: mscc: enable VSC8501/2 RGMII RX clock
> Its my first patch re-submission, so sorry for the noob question:
> Should I include your "pw-bot: changes-requested" tag with the third
> patch? Probably not.
No.
There is a robot listening to emails, and when it sees pw-bot: It uses
the label to change the state of the patch in patchworks:
https://patchwork.kernel.org/project/netdevbpf/list/
The robot does have some basic authentication, so it should actually
ignore such a line from you, since you are not a Maintainer. But even
so, you don't want to make your own new patches as needing changes.
Andrew
Powered by blists - more mailing lists