All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <landley@trommello.org>
To: Bill Davidsen <davidsen@tmr.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org,
	Suparna Bhattacharya <suparna@in.ibm.com>,
	Petr Vandrovec <VANDROVE@vc.cvut.cz>,
	fastboot@osdl.org, Werner Almesberger <wa@almesberger.net>
Subject: Re: kexec for 2.5.44 (Who do I send this to?)
Date: Sun, 20 Oct 2002 18:02:54 -0500	[thread overview]
Message-ID: <200210201802.54991.landley@trommello.org> (raw)
In-Reply-To: <Pine.LNX.3.96.1021019151759.29078I-100000@gatekeeper.tmr.com>

On Saturday 19 October 2002 14:23, Bill Davidsen wrote:
> On 19 Oct 2002, Eric W. Biederman wrote:
> > The kexec code has gone through a fairly decent review, and all known
> > bugs are resolved.  There are still BIOS's that don't work after you have
> > run a kernel but that is an entirely different problem.
> >
> > My real question: With Linus off on vacation my real question is who
> > should I send this to?
>
> I believe Linus explicitly said he wasn't going to tell anyone, which
> means we're back to the days of "through it on the list over and over
> until someone admits to seeing it." Or send it to everyone who might be
> willing to push it to Linus when he gets back.
>
> By not accepting stuff at this point I would guess that the defacto freeze
> is here. Hope I'm wrong, there is some good stuff which would be ready by
> Oct 31.

Linus implied there would be one more last minute surge of merges.  (Why else 
have people patch hoovering for anything other than bugs in the meantime?)

Probably the best thing to do is assemble a list of candidates, well-tested 
patches that have been up on the list and with as many endorsements from 
testers going "AOL!" as possible.  The last go-through when lkinus gets back 
is probably going to be simple thumbs-up thumbs down on each entry in the 
pending feature list, and then into the 3.0-pre series...

The current "pending feature list" would probably be here:

http://kernelnewbies.org/status/

Specifically:

o in -ac PCMCIA Zoom video support (Alan Cox) 
o in -ac Device mapper for Logical Volume Manager (LVM2)  (LVM2 team) 
o in -mm VM large page support  (Many people) 
o in -mm  Page table sharing  (Daniel Phillips, Dave McCracken) 

o Ready  Build option for Linux Trace Toolkit (LTT) (Karim Yaghmour) 
o Ready Dynamic Probes (dprobes team) 
o Ready Zerocopy NFS (Hirokazu Takahashi) 
o Ready High resolution timers (George Anzinger, etc.) 
o Ready EVMS (Enterprise Volume Management System) (EVMS team) 
o Ready Linux Kernel Crash Dumps (Matt Robinson, LKCD team) 
o Ready Rewrite of the console layer (James Simmons) 

If you're not on this list, contact Guillaume, or start your own list of 
"final merge candidates"...

Rob

  parent reply	other threads:[~2002-10-21  3:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-19 10:10 kexec for 2.5.44 (Who do I send this to?) 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 [this message]
2002-10-21 12:31   ` Alan Cox
2002-10-21 14:51     ` Eric W. Biederman
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=200210201802.54991.landley@trommello.org \
    --to=landley@trommello.org \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=davidsen@tmr.com \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suparna@in.ibm.com \
    --cc=wa@almesberger.net \
    /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.