From: Andrew Lunn <andrew@lunn.ch>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Yang Li <yang.lee@linux.alibaba.com>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [net-next PATCH v4 3/3] leds: trigger: netdev: expose hw_control status via sysfs
Date: Sun, 18 Jun 2023 22:15:40 +0200 [thread overview]
Message-ID: <c8065155-096f-4939-9cef-e419a0371e93@lunn.ch> (raw)
In-Reply-To: <20230617115355.22868-4-ansuelsmth@gmail.com>
On Sat, Jun 17, 2023 at 01:53:55PM +0200, Christian Marangi wrote:
> Expose hw_control status via sysfs for the netdev trigger to give
> userspace better understanding of the current state of the trigger and
> the LED.
>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2023-06-18 20:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 11:53 [net-next PATCH v4 0/3] leds: trigger: netdev: add additional modes Christian Marangi
2023-06-17 11:53 ` [net-next PATCH v4 1/3] leds: trigger: netdev: add additional specific link speed mode Christian Marangi
2023-06-17 11:53 ` [net-next PATCH v4 2/3] leds: trigger: netdev: add additional specific link duplex mode Christian Marangi
2023-06-18 20:10 ` Andrew Lunn
2023-06-17 11:53 ` [net-next PATCH v4 3/3] leds: trigger: netdev: expose hw_control status via sysfs Christian Marangi
2023-06-18 20:15 ` Andrew Lunn [this message]
2023-06-19 10:40 ` [net-next PATCH v4 0/3] leds: trigger: netdev: add additional modes Lee Jones
2023-06-19 13:34 ` Andrew Lunn
2023-06-20 10:26 ` Lee Jones
2023-06-20 13:59 ` Andrew Lunn
2023-06-21 14:56 ` Lee Jones
2023-06-19 20:27 ` Simon Horman
2023-06-19 20:48 ` Christian Marangi
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=c8065155-096f-4939-9cef-e419a0371e93@lunn.ch \
--to=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=davem@davemloft.net \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=yang.lee@linux.alibaba.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
all inboxes | Powered by JetHome®