[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180629082439.GA15660@kroah.com>
Date: Fri, 29 Jun 2018 04:24:39 -0400
From: Greg KH <gregkh@...uxfoundation.org>
To: Pavel Machek <pavel@....cz>
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, 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 :)
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.
If you don't want this cluttering up your kernel, don't built it in.
I think it should be taken as-is (well, with the few changes already
recommended).
thanks,
greg k-h
Powered by blists - more mailing lists