From: Andi Kleen <andi@firstfloor.org>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
cluster-devel@redhat.com, linux-kernel@vger.kernel.org,
rpurdie@rpsys.net
Subject: Re: GFS2: Add LED support to GFS2
Date: Wed, 22 Jul 2009 16:55:34 +0200 [thread overview]
Message-ID: <20090722145534.GA6035@basil.fritz.box> (raw)
In-Reply-To: <1248274288.3298.5.camel@localhost.localdomain>
> It would be difficult to make that generic since the errors and the
> resulting actions which can be taken vary from fs to fs. The main reason
> that I didn't do it at this point in time is that the GFS2 error
> handling needs revising anyway, and once that is done (probably with an
> errors= option similar to ext2/3/4) it might be possible to think about
> LED support for that,
I was thinking to have a couple of generic functions like:
log_activity()
error_happened()
...
that everyone could call.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-07-22 14:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 10:56 [Cluster-devel] GFS2: Add LED support to GFS2 Steven Whitehouse
2009-07-22 10:56 ` Steven Whitehouse
2009-07-22 14:46 ` Andi Kleen
2009-07-22 14:51 ` [Cluster-devel] " Steven Whitehouse
2009-07-22 14:51 ` Steven Whitehouse
2009-07-22 14:55 ` Andi Kleen [this message]
2009-07-22 15:02 ` [Cluster-devel] " Steven Whitehouse
2009-07-22 15:02 ` Steven Whitehouse
2009-07-22 15:15 ` Andi Kleen
2009-07-22 15:24 ` [Cluster-devel] " Steven Whitehouse
2009-07-22 15:24 ` Steven Whitehouse
2009-07-22 15:33 ` Andi Kleen
2009-07-22 15:50 ` Valdis.Kletnieks
2009-07-29 15:08 ` [Cluster-devel] " Pavel Machek
2009-07-29 15:08 ` Pavel Machek
2009-07-29 15:52 ` [Cluster-devel] " Steven Whitehouse
2009-07-29 15:52 ` Steven Whitehouse
2009-07-31 11:53 ` [Cluster-devel] " Pavel Machek
2009-07-31 11:53 ` Pavel Machek
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=20090722145534.GA6035@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=cluster-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=swhiteho@redhat.com \
/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.