From: Pavel Machek <pavel@ucw.cz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andreas Klinger <ak@it-klinger.de>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Ben Whitten <ben.whitten@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Willy Tarreau <w@1wt.eu>,
Philippe Ombredanne <pombredanne@nexb.com>,
Greg KH <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-leds@vger.kernel.org
Subject: Re: [PATCH] leds: ledtrig-morse: send out morse code
Date: Fri, 29 Jun 2018 10:07:17 +0200 [thread overview]
Message-ID: <20180629080717.GA12112@amd> (raw)
In-Reply-To: <CAMuHMdW1NX=BwJE0eauRLkRj1se4iRNGdxHXeajNQ-dKDhnPKw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 527 bytes --]
Hi!
> > There's no reason 2. should be in kernel ("mechanism, not policy").
> >
> > Given 1. is not really more complicated than the morse
> > trigger... please just help with pattern trigger if you want this to
> > happen.
>
> Ah, you want to do the conversion to morse code in userspace?
> Yes, that makes sense.
Yes, that's what I want.
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 --]
next prev parent reply other threads:[~2018-06-29 8:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 13:42 [PATCH] leds: ledtrig-morse: send out morse code Andreas Klinger
2018-06-28 13:54 ` Greg KH
2018-06-28 15:36 ` Geert Uytterhoeven
2018-06-28 18:21 ` Willy Tarreau
2018-06-28 18:56 ` Pavel Machek
2018-06-28 20:29 ` Andreas Klinger
2018-06-28 20:45 ` Pavel Machek
2018-06-29 6:41 ` Andreas Klinger
2018-06-29 7:17 ` Pavel Machek
2018-06-29 7:21 ` Geert Uytterhoeven
2018-06-29 7:29 ` Pavel Machek
2018-06-29 7:48 ` Geert Uytterhoeven
2018-06-29 8:07 ` Pavel Machek [this message]
2018-06-29 8:24 ` Greg KH
2018-06-29 9:23 ` Pavel Machek
2018-06-28 20:33 ` Andreas Klinger
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=20180629080717.GA12112@amd \
--to=pavel@ucw.cz \
--cc=ak@it-klinger.de \
--cc=ben.whitten@gmail.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--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.