The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Jens Axboe <axboe@suse.de>
Cc: Richard Purdie <rpurdie@rpsys.net>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 10/11] LED: Add IDE disk activity LED trigger
Date: Thu, 2 Feb 2006 12:07:38 +0100	[thread overview]
Message-ID: <20060202110738.GA2151@elf.ucw.cz> (raw)
In-Reply-To: <20060131203552.GG4215@suse.de>

Hi!

> > These solutions are going to end up with a lot of unused led triggers on
> > any given system. 
> 
> Perhaps a generic solution isn't feasible, because this isn't really a
> generic problem. The LED stuff has very limited use - you mention
> embedded platforms, perhaps they should just be doing this on their
> own?

LEDs need userland API to be useful in some cases (mail LED). At that
point saying "everybody make your own API" is very bad idea.

(And we have old, ARM-private API at least, already. Idea is to do it
once and do it right).
								Pavel
-- 
Thanks, Sharp!

  parent reply	other threads:[~2006-02-02 11:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31 13:41 [PATCH 10/11] LED: Add IDE disk activity LED trigger Richard Purdie
2006-01-31 14:46 ` Bartlomiej Zolnierkiewicz
2006-01-31 16:21   ` Richard Purdie
2006-01-31 17:44     ` Bartlomiej Zolnierkiewicz
2006-01-31 20:29       ` Jens Axboe
2006-01-31 22:08       ` Benjamin Herrenschmidt
2006-01-31 23:39         ` Richard Purdie
2006-02-04 15:29       ` Richard Purdie
2006-01-31 20:35     ` Jens Axboe
2006-01-31 21:22       ` Jordan Crouse
2006-02-01  0:12         ` Matt Reimer
2006-02-02  1:32         ` Adrian Bunk
2006-01-31 22:03       ` [PATCH 10/11] " Richard Purdie
2006-02-02 11:07       ` Pavel Machek [this message]
2006-02-01 16:09 ` Jan Engelhardt
2006-02-04  9:54   ` Jan-Benedict Glaw

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=20060202110738.GA2151@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=axboe@suse.de \
    --cc=bzolnier@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    /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