From: ebiederm@xmission.com (Eric W. Biederman)
To: vgoyal@in.ibm.com
Cc: Preben Traerup <Preben.Trarup@ericsson.com>,
fastboot@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] [PATCH] kdump: add a missing notifier before crashing
Date: Mon, 19 Jun 2006 12:45:17 -0600 [thread overview]
Message-ID: <m1mzc9gf2a.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060619181915.GD8172@in.ibm.com> (Vivek Goyal's message of "Mon, 19 Jun 2006 14:19:15 -0400")
Vivek Goyal <vgoyal@in.ibm.com> writes:
> On Mon, Jun 19, 2006 at 11:50:24AM -0600, Eric W. Biederman wrote:
>>
>> Having notifiers and being able to disable them is designing for an
>> unspecified case. We need to concentrate on the fundamentals here.
>> Do any of these crash notifiers make sense?
>>
>
> Agreed. That makes sense. Probably folks who want this functionality
> should also post the code which they would like to run from inside the
> notifiers so that requirement is understood more clearly.
Which is why I will be happy to see patch that call the functions directly.
Without the notification layer.
If they make sense I will even be happy to see those patches go upstream.
Eric
next prev parent reply other threads:[~2006-06-19 18:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 11:16 Akiyama, Nobuyuki
2006-06-16 6:28 ` [Fastboot] " Eric W. Biederman
2006-06-16 12:15 ` Akiyama, Nobuyuki
2006-06-16 16:37 ` Eric W. Biederman
2006-06-19 7:30 ` Akiyama, Nobuyuki
2006-06-19 12:47 ` Eric W. Biederman
2006-06-19 13:28 ` Preben Traerup
2006-06-19 16:49 ` Eric W. Biederman
2006-06-19 17:07 ` Vivek Goyal
2006-06-19 17:50 ` Eric W. Biederman
2006-06-19 18:19 ` Vivek Goyal
2006-06-19 18:45 ` Eric W. Biederman [this message]
2006-06-20 3:46 ` Akiyama, Nobuyuki
2006-06-20 3:39 ` Akiyama, Nobuyuki
2006-07-04 12:33 Akiyama, Nobuyuki
2006-07-05 16:14 ` [Fastboot] " Eric W. Biederman
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=m1mzc9gf2a.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=Preben.Trarup@ericsson.com \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®