From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Marek_Beh=C3=BAn_=3Ckabel=40kernel=2Eorg=3E?=@ci.codeaurora.org
Cc: kuba@kernel.org, netdev@vger.kernel.org, andrew@lunn.ch,
ansuelsmth@gmail.com
Subject: Re: [PATCH net] leds: trigger: netdev: rename 'hw_control' sysfs entry to 'offloaded'
Date: Tue, 22 Aug 2023 18:10:26 +0000 [thread overview]
Message-ID: <169272782671.18530.3096881075670234902.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230821121453.30203-1-kabel@kernel.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 21 Aug 2023 14:14:53 +0200 you wrote:
> Commit b655892ffd6d ("leds: trigger: netdev: expose hw_control status
> via sysfs") exposed to sysfs the flag that tells whether the LED trigger
> is offloaded to hardware, under the name "hw_control", since that is the
> name under which this setting is called in the code.
>
> Everywhere else in kernel when some work that is normally done in
> software can be made to be done by hardware instead, we use the word
> "offloading" to describe this, e.g. "LED blinking is offloaded to
> hardware".
>
> [...]
Here is the summary with links:
- [net] leds: trigger: netdev: rename 'hw_control' sysfs entry to 'offloaded'
https://git.kernel.org/netdev/net/c/44f0fb8dfe26
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-08-22 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 12:14 [PATCH net] leds: trigger: netdev: rename 'hw_control' sysfs entry to 'offloaded' Marek Behún
2023-08-21 13:20 ` Andrew Lunn
2023-08-22 18:10 ` patchwork-bot+netdevbpf [this message]
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=169272782671.18530.3096881075670234902.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Marek_Beh=C3=BAn_=3Ckabel=40kernel=2Eorg=3E?=@ci.codeaurora.org \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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).