From: ebiederm@xmission.com (Eric W. Biederman)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kexec for 2.5.44 (Who do I send this to?)
Date: 21 Oct 2002 08:51:08 -0600 [thread overview]
Message-ID: <m1fzuzvo9v.fsf@frodo.biederman.org> (raw)
In-Reply-To: <1035203491.27259.71.camel@irongate.swansea.linux.org.uk>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> I will start picking stuff up now I'm back and catching up on email
> (I've been away for a week). I'm not however interested in kexec or ltt
> or a lot of the other large stuff so don't bother resending me that kind
> of thing.
>
> I really want to collect up bug fixes/compile fixes/driver updates and
> small but ready to merge stuff like the console updates if James Simmons
> is paying attention.
I am half insulted. kexec is about as ready to merge as it comes...
But I do admit the code to safely position the new kernel safely in
memory safely is a little large.
And there is not a lot of point in widespread testing of kexec until
the drivers get fixed to actually do something when device_shutdown
runs. As drivers that don't shutdown properly are a fairly serious
issue.
If you are interested I can break out my reboot time hardware bug
fixes, and send you those.
Eric
next prev parent reply other threads:[~2002-10-21 14:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 10:10 Eric W. Biederman
2002-10-19 19:23 ` Bill Davidsen
2002-10-19 21:36 ` Eric W. Biederman
2002-10-20 23:02 ` Rob Landley
2002-10-21 12:31 ` Alan Cox
2002-10-21 14:51 ` Eric W. Biederman [this message]
2002-10-21 20:54 ` Bill Davidsen
2002-10-20 19:09 ` Pavel Machek
2002-10-26 13:54 ` Eric W. Biederman
2002-10-27 17:44 ` Eric W. Biederman
2002-10-27 22:51 ` Eric W. Biederman
2002-10-30 14:02 ` Pavel Machek
2002-10-30 15:53 ` Eric W. Biederman
2002-10-28 8:16 ` [CFT] [PATCH] kexec 2.5.44 (minimal) Eric W. Biederman
2002-10-30 22:41 ` Andy Pfiffer
2002-10-31 3:59 ` 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=m1fzuzvo9v.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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
Powered by JetHome