From: Andrew Lunn <andrew@lunn.ch>
To: Daniel Golle <daniel@makrotopia.org>
Cc: netdev <netdev@vger.kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <rmk+kernel@armlinux.org.uk>,
Simon Horman <simon.horman@corigine.com>,
Christian Marangi <ansuelsmth@gmail.com>
Subject: Re: [PATCH net-next v3 0/4] Support offload LED blinking to PHY.
Date: Wed, 9 Aug 2023 18:27:29 +0200 [thread overview]
Message-ID: <bd83fb99-abdd-4b4d-b6b6-6b8cef9fc22f@lunn.ch> (raw)
In-Reply-To: <ZNO6hfjrJthoIUi9@makrotopia.org>
> Overall I believe this is good to go, however, what remains
> unresolved is the chicken-egg when assigning the 'netdev' trigger
> using linux,default-trigger in device tree:
Agreed. This is pretty high up my TODO list to look at.
Thanks for the tested-by.
Andrew
next prev parent reply other threads:[~2023-08-09 16:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 21:04 [PATCH net-next v3 0/4] Support offload LED blinking to PHY Andrew Lunn
2023-08-08 21:04 ` [PATCH net-next v3 1/4] led: trig: netdev: Fix requesting offload device Andrew Lunn
2023-08-08 21:04 ` [PATCH net-next v3 2/4] net: phy: phy_device: Call into the PHY driver to set LED offload Andrew Lunn
2023-08-08 21:04 ` [PATCH net-next v3 3/4] net: phy: marvell: Add support for offloading LED blinking Andrew Lunn
2023-08-08 21:04 ` [PATCH net-next v3 4/4] leds: trig-netdev: Disable offload on deactivation of trigger Andrew Lunn
2023-08-09 7:46 ` Simon Horman
2023-08-09 16:10 ` [PATCH net-next v3 0/4] Support offload LED blinking to PHY Daniel Golle
2023-08-09 16:27 ` Andrew Lunn [this message]
2023-08-11 0:40 ` patchwork-bot+netdevbpf
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=bd83fb99-abdd-4b4d-b6b6-6b8cef9fc22f@lunn.ch \
--to=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=daniel@makrotopia.org \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=simon.horman@corigine.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;
as well as URLs for NNTP newsgroup(s).