From: Amy Parker <apark0006@student.cerritos.edu>
To: pavel@ucw.cz
Cc: Amy Parker <apark0006@student.cerritos.edu>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] drivers/leds/TODO: update TODO to reflect changes
Date: Thu, 15 Jul 2021 14:18:57 -0700 [thread overview]
Message-ID: <fd4841b1fa09bfefb707563d85a2388d41c3b424.1626383424.git.apark0006@student.cerritos.edu> (raw)
In-Reply-To: <cover.1626383424.git.apark0006@student.cerritos.edu>
The previous commit in this chain (swap led_brightness from enum to
typedef) fixed the removed issue in this TODO. This patch updates
the TODO to indicate this.
Signed-off-by: Amy Parker <apark0006@student.cerritos.edu>
---
drivers/leds/TODO | 4 ----
1 file changed, 4 deletions(-)
diff --git a/drivers/leds/TODO b/drivers/leds/TODO
index e1d771513b98..7b97bb733392 100644
--- a/drivers/leds/TODO
+++ b/drivers/leds/TODO
@@ -1,10 +1,6 @@
-*- org -*-
* On/off LEDs should have max_brightness of 1
-* Get rid of led_brightness
-
-It is really an integer, as maximum is configurable. Get rid of it, or
-make it into typedef or something.
* Review atomicity requirements in LED subsystem
--
2.31.1
prev parent reply other threads:[~2021-07-15 21:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 21:18 [PATCH 0/2] leds: change led_brightness definition from enum to typedef Amy Parker
2021-07-15 21:18 ` [PATCH 1/2] swap led_brightness " Amy Parker
2021-07-16 0:41 ` kernel test robot
2021-07-16 2:14 ` kernel test robot
2021-07-16 3:11 ` Amy Parker
2021-07-16 21:07 ` Amy Parker
2021-07-16 21:43 ` Randy Dunlap
2021-07-19 12:05 ` Pavel Machek
2021-07-19 7:16 ` Geert Uytterhoeven
2021-07-19 8:40 ` Geert Uytterhoeven
2021-08-03 21:38 ` Pavel Machek
2021-07-19 8:05 ` Dan Carpenter
2021-07-19 8:21 ` Dan Carpenter
2021-07-19 12:08 ` Pavel Machek
2021-07-15 21:18 ` Amy Parker [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=fd4841b1fa09bfefb707563d85a2388d41c3b424.1626383424.git.apark0006@student.cerritos.edu \
--to=apark0006@student.cerritos.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).