From: Christian Marangi <ansuelsmth@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
John Crispin <john@phrozen.org>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Lee Jones <lee@kernel.org>,
linux-leds@vger.kernel.org
Subject: Re: [net-next PATCH 09/11] dt-bindings: net: dsa: qca8k: add LEDs definition example
Date: Wed, 8 Mar 2023 20:23:03 +0100 [thread overview]
Message-ID: <6408e09b.050a0220.e7ce5.1e98@mx.google.com> (raw)
In-Reply-To: <36169a8a-d418-6d7e-b64c-a7c346b9a218@linaro.org>
On Wed, Mar 08, 2023 at 08:09:34PM +0100, Krzysztof Kozlowski wrote:
> On 08/03/2023 20:02, Christian Marangi wrote:
> > On Wed, Mar 08, 2023 at 07:49:26PM +0100, Krzysztof Kozlowski wrote:
> >> On 08/03/2023 14:57, Andrew Lunn wrote:
> >>> On Wed, Mar 08, 2023 at 11:58:33AM +0100, Krzysztof Kozlowski wrote:
> >>>> On 07/03/2023 18:00, Christian Marangi wrote:
> >>>>> Add LEDs definition example for qca8k Switch Family to describe how they
> >>>>> should be defined for a correct usage.
> >>>>>
> >>>>> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> >>>>
> >>>> Where is the changelog? This was v8 already! What happened with all
> >>>> review, changes?
> >>>
> >>> Did you read patch 0?
> >>>
> >>> We have decided to start again, starting small and working up. This
> >>> patchset just adds plain, boring LEDs. No acceleration, on hardware
> >>> offload. Just on/off, and fixed blink.
> >>
> >> Sure, but the patch is carried over. So what happened with all its
> >> feedback? Was there or was not? How can we know?
> >>
> >
> > The history of the old series is a bit sad, not enough review, another
> > dev asking for a different implementation and me doing an hybrid to
> > reach a common point (and then disappear intro oblivion)...
> >
> > Short story is that this current series have nothing related to the HW
> > offload feature and only in v7 it was asked to put the LED nodes in
> > ethernet-phy.yaml
> >
> > I can put in the cover letter of v2 of this series the changelog of the
> > previous series but they would only be related to other part that are
> > not related to this.
> >
> > Just to give you some context and explain why the changelog was dropped.
>
> I am less interested in the changelog of entire patchset but of the
> patches which are for me to review. Sending vX as v1 suggests that all
> previous review work on this patch could be in some limbo state. Maybe
> nothing happened in all previous version, but it's now my task to dig it?
>
OK, if you are intrested only on the DT changes I can list:
From v0 to v6:
- There was only qca8k Documentation addition for the leds node.
Some extra binding were dropped due to implementation change but they
were only specific to qca8k.
In v7:
- The default-trigger for netdev was introduced (this caused some
warning for missing netdev trigger for that binding)
- It was suggested and asked to make the LEDs generic and add
Documentration for phy-ethernet.yaml
In v8:
- The netdev trigger was added to the list of accepted default-trigger
- The Documentation for phy-ethernet.yaml was added
Then we decided to "reboot" the series and:
In v1:
- The default-trigger is dropped (will be introduced later when the work
for the netdev trigger will be done)
- We use the default state to "keep"
This should be the entire changelog excluding some changed things done
from v0 to v6 with low review and implementation changed at least 3
times during the life of that series.
> This is why you have "---" for the patch changelog.
--
Ansuel
WARNING: multiple messages have this Message-ID (diff)
From: Christian Marangi <ansuelsmth@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
John Crispin <john@phrozen.org>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Lee Jones <lee@kernel.org>,
linux-leds@vger.kernel.org
Subject: Re: [net-next PATCH 09/11] dt-bindings: net: dsa: qca8k: add LEDs definition example
Date: Wed, 8 Mar 2023 20:23:03 +0100 [thread overview]
Message-ID: <6408e09b.050a0220.e7ce5.1e98@mx.google.com> (raw)
In-Reply-To: <36169a8a-d418-6d7e-b64c-a7c346b9a218@linaro.org>
On Wed, Mar 08, 2023 at 08:09:34PM +0100, Krzysztof Kozlowski wrote:
> On 08/03/2023 20:02, Christian Marangi wrote:
> > On Wed, Mar 08, 2023 at 07:49:26PM +0100, Krzysztof Kozlowski wrote:
> >> On 08/03/2023 14:57, Andrew Lunn wrote:
> >>> On Wed, Mar 08, 2023 at 11:58:33AM +0100, Krzysztof Kozlowski wrote:
> >>>> On 07/03/2023 18:00, Christian Marangi wrote:
> >>>>> Add LEDs definition example for qca8k Switch Family to describe how they
> >>>>> should be defined for a correct usage.
> >>>>>
> >>>>> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> >>>>
> >>>> Where is the changelog? This was v8 already! What happened with all
> >>>> review, changes?
> >>>
> >>> Did you read patch 0?
> >>>
> >>> We have decided to start again, starting small and working up. This
> >>> patchset just adds plain, boring LEDs. No acceleration, on hardware
> >>> offload. Just on/off, and fixed blink.
> >>
> >> Sure, but the patch is carried over. So what happened with all its
> >> feedback? Was there or was not? How can we know?
> >>
> >
> > The history of the old series is a bit sad, not enough review, another
> > dev asking for a different implementation and me doing an hybrid to
> > reach a common point (and then disappear intro oblivion)...
> >
> > Short story is that this current series have nothing related to the HW
> > offload feature and only in v7 it was asked to put the LED nodes in
> > ethernet-phy.yaml
> >
> > I can put in the cover letter of v2 of this series the changelog of the
> > previous series but they would only be related to other part that are
> > not related to this.
> >
> > Just to give you some context and explain why the changelog was dropped.
>
> I am less interested in the changelog of entire patchset but of the
> patches which are for me to review. Sending vX as v1 suggests that all
> previous review work on this patch could be in some limbo state. Maybe
> nothing happened in all previous version, but it's now my task to dig it?
>
OK, if you are intrested only on the DT changes I can list:
From v0 to v6:
- There was only qca8k Documentation addition for the leds node.
Some extra binding were dropped due to implementation change but they
were only specific to qca8k.
In v7:
- The default-trigger for netdev was introduced (this caused some
warning for missing netdev trigger for that binding)
- It was suggested and asked to make the LEDs generic and add
Documentration for phy-ethernet.yaml
In v8:
- The netdev trigger was added to the list of accepted default-trigger
- The Documentation for phy-ethernet.yaml was added
Then we decided to "reboot" the series and:
In v1:
- The default-trigger is dropped (will be introduced later when the work
for the netdev trigger will be done)
- We use the default state to "keep"
This should be the entire changelog excluding some changed things done
from v0 to v6 with low review and implementation changed at least 3
times during the life of that series.
> This is why you have "---" for the patch changelog.
--
Ansuel
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-03-08 19:23 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 17:00 [net-next PATCH 00/11] net: Add basic LED support for switch/phy Christian Marangi
2023-03-07 17:00 ` Christian Marangi
2023-03-07 17:00 ` [net-next PATCH 01/11] net: dsa: qca8k: add LEDs basic support Christian Marangi
2023-03-07 17:00 ` Christian Marangi
2023-03-07 23:16 ` Andrew Lunn
2023-03-07 23:16 ` Andrew Lunn
2023-03-07 17:57 ` Christian Marangi
2023-03-07 17:57 ` Christian Marangi
2023-03-08 0:49 ` Andrew Lunn
2023-03-08 0:49 ` Andrew Lunn
2023-03-07 19:41 ` Christian Marangi
2023-03-07 19:41 ` Christian Marangi
2023-03-08 1:07 ` Andrew Lunn
2023-03-08 1:07 ` Andrew Lunn
2023-03-16 22:07 ` kernel test robot
2023-03-16 22:07 ` kernel test robot
2023-03-07 17:00 ` [net-next PATCH 02/11] net: dsa: qca8k: add LEDs blink_set() support Christian Marangi
2023-03-07 17:00 ` Christian Marangi
2023-03-07 23:16 ` Andrew Lunn
2023-03-07 23:16 ` Andrew Lunn
2023-03-07 17:00 ` [net-next PATCH 03/11] net: phy: Add a binding for PHY LEDs Christian Marangi
2023-03-07 17:00 ` Christian Marangi
2023-03-07 23:17 ` Andrew Lunn
2023-03-07 23:17 ` Andrew Lunn
2023-03-07 18:00 ` Christian Marangi
2023-03-07 18:00 ` Christian Marangi
2023-03-08 0:54 ` Andrew Lunn
2023-03-08 0:54 ` Andrew Lunn
2023-03-07 17:00 ` [net-next PATCH 04/11] net: phy: phy_device: Call into the PHY driver to set LED brightness Christian Marangi
2023-03-07 17:00 ` Christian Marangi
2023-03-07 17:00 ` [net-next PATCH 05/11] net: phy: marvell: Add software control of the LEDs Christian Marangi
2023-03-07 17:00 ` Christian Marangi
2023-03-07 17:00 ` [net-next PATCH 06/11] net: phy: phy_device: Call into the PHY driver to set LED blinking Christian Marangi
2023-03-07 17:00 ` Christian Marangi
2023-03-07 17:00 ` [net-next PATCH 07/11] net: phy: marvell: Implement led_blink_set() Christian Marangi
2023-03-07 17:00 ` Christian Marangi
2023-03-07 17:00 ` [net-next PATCH 08/11] dt-bindings: net: dsa: dsa-port: Document support for LEDs node Christian Marangi
2023-03-07 17:00 ` Christian Marangi
2023-03-08 1:00 ` Andrew Lunn
2023-03-08 1:00 ` Andrew Lunn
2023-03-08 18:58 ` Krzysztof Kozlowski
2023-03-08 18:58 ` Krzysztof Kozlowski
2023-03-07 17:00 ` [net-next PATCH 09/11] dt-bindings: net: dsa: qca8k: add LEDs definition example Christian Marangi
2023-03-07 17:00 ` Christian Marangi
2023-03-08 10:58 ` Krzysztof Kozlowski
2023-03-08 10:58 ` Krzysztof Kozlowski
2023-03-08 13:57 ` Andrew Lunn
2023-03-08 13:57 ` Andrew Lunn
2023-03-08 18:49 ` Krzysztof Kozlowski
2023-03-08 18:49 ` Krzysztof Kozlowski
2023-03-08 19:02 ` Christian Marangi
2023-03-08 19:02 ` Christian Marangi
2023-03-08 19:09 ` Krzysztof Kozlowski
2023-03-08 19:09 ` Krzysztof Kozlowski
2023-03-08 19:23 ` Christian Marangi [this message]
2023-03-08 19:23 ` Christian Marangi
2023-03-08 19:42 ` Andrew Lunn
2023-03-08 19:42 ` Andrew Lunn
2023-03-07 17:00 ` [net-next PATCH 10/11] dt-bindings: net: phy: Document support for LEDs node Christian Marangi
2023-03-07 17:00 ` Christian Marangi
2023-03-08 1:01 ` Andrew Lunn
2023-03-08 1:01 ` Andrew Lunn
2023-03-08 11:00 ` Krzysztof Kozlowski
2023-03-08 11:00 ` Krzysztof Kozlowski
2023-03-08 18:56 ` Krzysztof Kozlowski
2023-03-08 18:56 ` Krzysztof Kozlowski
2023-03-08 18:56 ` Krzysztof Kozlowski
2023-03-08 18:56 ` Krzysztof Kozlowski
2023-03-08 19:03 ` Christian Marangi
2023-03-08 19:03 ` Christian Marangi
2023-03-07 17:00 ` [net-next PATCH 11/11] arm: mvebu: dt: Add PHY LED support for 370-rd WAN port Christian Marangi
2023-03-07 17:00 ` Christian Marangi
2023-03-07 23:20 ` Andrew Lunn
2023-03-07 23:20 ` Andrew Lunn
2023-03-07 18:03 ` Christian Marangi
2023-03-07 18:03 ` Christian Marangi
2023-03-08 1:20 ` [net-next PATCH 00/11] net: Add basic LED support for switch/phy Andrew Lunn
2023-03-08 1:20 ` Andrew Lunn
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=6408e09b.050a0220.e7ce5.1e98@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=hkallweit1@gmail.com \
--cc=john@phrozen.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.