From: ebiederm@xmission.com (Eric W. Biederman)
To: Takenori Nagano <t-nagano@ah.jp.nec.com>
Cc: k-miyoshi@cb.jp.nec.com, Bernhard Walle <bwalle@suse.de>,
kdb@oss.sgi.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, vgoyal@in.ibm.com,
Keith Owens <kaos@ocs.com.au>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/2] add new notifier function
Date: Fri, 05 Oct 2007 07:01:17 -0600 [thread overview]
Message-ID: <m1641llnqa.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <4704D09D.6080503@ah.jp.nec.com> (Takenori Nagano's message of "Thu, 04 Oct 2007 20:38:05 +0900")
Takenori Nagano <t-nagano@ah.jp.nec.com> writes:
> Hi,
>
> These patches add new notifier function and implement it to panic_notifier_list.
> We used the hardcoded notifier chain so far, but it was not flexible. New
> notifier is very flexible, because user can change a list of order by debugfs.
How is the lack of flexibility a problem?
Specifics please.
My impression is that the purpose of this patchset is to build
infrastructure to sort out a conflict between kdb and the kexec code,
which it does not do, and it can not do if it does not own up to
it's real purpose.
If I am correct in understanding the purpose of this patchset it does
not even address the problem it is aimed at solving.
Eric
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: Takenori Nagano <t-nagano@ah.jp.nec.com>
Cc: linux-kernel@vger.kernel.org, vgoyal@in.ibm.com,
k-miyoshi@cb.jp.nec.com, kexec@lists.infradead.org,
Bernhard Walle <bwalle@suse.de>, Keith Owens <kaos@ocs.com.au>,
Andrew Morton <akpm@linux-foundation.org>,
kdb@oss.sgi.com
Subject: Re: [PATCH 0/2] add new notifier function
Date: Fri, 05 Oct 2007 07:01:17 -0600 [thread overview]
Message-ID: <m1641llnqa.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <4704D09D.6080503@ah.jp.nec.com> (Takenori Nagano's message of "Thu, 04 Oct 2007 20:38:05 +0900")
Takenori Nagano <t-nagano@ah.jp.nec.com> writes:
> Hi,
>
> These patches add new notifier function and implement it to panic_notifier_list.
> We used the hardcoded notifier chain so far, but it was not flexible. New
> notifier is very flexible, because user can change a list of order by debugfs.
How is the lack of flexibility a problem?
Specifics please.
My impression is that the purpose of this patchset is to build
infrastructure to sort out a conflict between kdb and the kexec code,
which it does not do, and it can not do if it does not own up to
it's real purpose.
If I am correct in understanding the purpose of this patchset it does
not even address the problem it is aimed at solving.
Eric
next prev parent reply other threads:[~2007-10-05 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 11:38 [PATCH 0/2] add new notifier function Takenori Nagano
2007-10-04 11:38 ` Takenori Nagano
2007-10-05 4:33 ` Vivek Goyal
2007-10-05 4:33 ` Vivek Goyal
2007-10-05 5:43 ` Takenori Nagano
2007-10-05 5:43 ` Takenori Nagano
2007-10-05 13:01 ` Eric W. Biederman [this message]
2007-10-05 13:01 ` Eric W. Biederman
2007-10-09 7:38 ` Takenori Nagano
2007-10-09 7:38 ` Takenori Nagano
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=m1641llnqa.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=bwalle@suse.de \
--cc=k-miyoshi@cb.jp.nec.com \
--cc=kaos@ocs.com.au \
--cc=kdb@oss.sgi.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=t-nagano@ah.jp.nec.com \
--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 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.