All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: Andreas Klinger <ak@it-klinger.de>,
	ben.whitten@gmail.com, geert+renesas@glider.be, w@1wt.eu,
	pombredanne@nexb.com, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH v2] leds: ledtrig-morse: send out morse code
Date: Wed, 4 Jul 2018 23:21:19 +0200	[thread overview]
Message-ID: <20180704212119.GA18063@amd> (raw)
In-Reply-To: <b10a8282-0297-8cd6-5d29-fb4adcf72366@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 628 bytes --]

Hi!

> >LED pattern trigger should be merged, instead.
> 
> We've already agreed in [0] upon pattern sysfs file, and related
> patch set [1] is just to be merged.
> 
> [0] https://lkml.org/lkml/2018/5/12/142
> [1] https://patchwork.kernel.org/patch/10495595/

Well, [1] is for LEDs that can do patterns in hardware. I'm aware of
that work.

I still believe that we want to do "trigger" that can do the same on
hardware that is not so lucky.

Best regards,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      reply	other threads:[~2018-07-04 21:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03 15:53 [PATCH v2] leds: ledtrig-morse: send out morse code Andreas Klinger
2018-07-03 18:43 ` Andy Shevchenko
2018-07-04  2:41   ` Willy Tarreau
2018-07-04  7:46     ` Geert Uytterhoeven
2018-07-04 16:25     ` Andy Shevchenko
2018-07-06  7:22     ` Geert Uytterhoeven
2018-07-04  6:53 ` Pavel Machek
2018-07-04  7:34   ` Willy Tarreau
2018-07-04 11:36     ` Greg KH
2018-07-04 18:19     ` Pavel Machek
2018-07-04 20:36       ` Jacek Anaszewski
2018-07-05 10:56       ` David Laight
2018-07-04 20:36   ` Jacek Anaszewski
2018-07-04 21:21     ` Pavel Machek [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=20180704212119.GA18063@amd \
    --to=pavel@ucw.cz \
    --cc=ak@it-klinger.de \
    --cc=ben.whitten@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pombredanne@nexb.com \
    --cc=w@1wt.eu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.