From: Oleksij Rempel <o.rempel@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Oleksij Rempel <o.rempel@pengutronix.de>
Subject: [PATCH v3 0/4] upstream led blinking rework
Date: Mon, 13 Mar 2017 10:33:35 +0100 [thread overview]
Message-ID: <20170313093339.12597-1-o.rempel@pengutronix.de> (raw)
changes v1:
- merge blinking/flashing and led_blink_pattern patches
- remove new unsued variables from structs
- add sanity check in the led command to avoid simultan -b anf -f options
changes v2:
- reword commit message in "led: add blinking/flashing..." patch
changes v3:
- reword "led-trigger: Allow multiple..." patch
- remove sanity check before free()
Sascha Hauer (4):
led: add blinking/flashing and led_blink_pattern interface
led: Add blink/flash to led command
led: trigger: Use led triggers
led-trigger: Allow multiple led triggers of the same type
commands/led.c | 44 ++++++++++++-
commands/trigger.c | 54 ++++++++--------
drivers/led/core.c | 101 ++++++++++++++++++++++++++++-
drivers/led/led-triggers.c | 157 ++++++++++++++++++++++++++++-----------------
include/led.h | 17 ++++-
5 files changed, 286 insertions(+), 87 deletions(-)
--
2.11.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2017-03-13 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 9:33 Oleksij Rempel [this message]
2017-03-13 9:33 ` [PATCH v3 1/4] led: add blinking/flashing and led_blink_pattern interface Oleksij Rempel
2017-03-13 9:33 ` [PATCH v3 2/4] led: Add blink/flash to led command Oleksij Rempel
2017-03-13 9:33 ` [PATCH v3 3/4] led: trigger: Use led triggers Oleksij Rempel
2017-03-13 9:33 ` [PATCH v3 4/4] led-trigger: Allow multiple led triggers of the same type Oleksij Rempel
2017-03-14 7:11 ` [PATCH v3 0/4] upstream led blinking rework Sascha Hauer
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=20170313093339.12597-1-o.rempel@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=barebox@lists.infradead.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