From: ebiederm@xmission.com (Eric W. Biederman)
To: Bill Davidsen <davidsen@tmr.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [KEXEC][2.5.63] Partially tested patches available
Date: 28 Feb 2003 10:03:20 -0700 [thread overview]
Message-ID: <m1smu8l4mf.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.3.96.1030228085058.25875B-100000@gatekeeper.tmr.com>
Bill Davidsen <davidsen@tmr.com> writes:
> On 27 Feb 2003, Eric W. Biederman wrote:
>
>
> > We need to get up some steam and see what it will take for Linus
> > to notice and actually get this patch included.
>
> I hate to say it, but "notice" and "include" are two different things. He
> noticed the "write oops to disk" feature, he just didn't like it. Linus is
> a great developer, but he has limited sys admin experience, if any.
> Hopefully he will think it's cool, but don't assume that if you can get
> his attention he will respond as you wish.
The code has already gotten tentative approval from Linus. And I suspect
the biggest reason it isn't in is that I have gotten distracted lately
and have not been asking for it to be included.
Being able to use this for processing panics is one of the side features
of kexec. Admittedly one of the more useful ones, but definitely not a core
feature.
Given the encouragement I have received until I actually get negative
feedback from Linus I will continue to figure it has not made it into
the kernel because Linus has limited hours in the day, and an overflowing
inbox.
Eric
next prev parent reply other threads:[~2003-02-28 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 0:53 [KEXEC][2.5.63] Partially tested patches available Andy Pfiffer
2003-02-27 11:50 ` Eric W. Biederman
2003-02-27 16:00 ` Martin J. Bligh
2003-02-27 16:01 ` Eric W. Biederman
2003-02-27 16:04 ` Martin J. Bligh
2003-02-28 14:10 ` Bill Davidsen
2003-02-28 17:03 ` Eric W. Biederman [this message]
2003-03-02 1:36 ` Werner Almesberger
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=m1smu8l4mf.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/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