[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180629092327.GB31718@amd>
Date: Fri, 29 Jun 2018 11:23:27 +0200
From: Pavel Machek <pavel@....cz>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>,
Andreas Klinger <ak@...klinger.de>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
Ben Whitten <ben.whitten@...il.com>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Willy Tarreau <w@....eu>,
Philippe Ombredanne <pombredanne@...b.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-leds@...r.kernel.org
Subject: Re: [PATCH] leds: ledtrig-morse: send out morse code
On Fri 2018-06-29 04:24:39, Greg KH wrote:
> On Fri, Jun 29, 2018 at 10:07:17AM +0200, Pavel Machek wrote:
> > 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.
>
> We all want a pony :)
I already have a pony :-).
> Seriously, this is a very simple module, works well, and makes some
> system's life much easier as there is no external dependancy on a
> text-to-morse-code library needed.
It still does not belong into kernel.
It is interesting. You deleted bluetooth driver people used from
staging because of "not enough cleanups" and you want me to maintain
text-to-morse-code in the kernel?!
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists