From: "Amit S. Kale" <amitkale@emsyssoft.com>
To: Tom Rini <trini@kernel.crashing.org>, Pavel Machek <pavel@ucw.cz>,
George Anzinger <george@mvista.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
KGDB bugreports <kgdb-bugreport@lists.sourceforge.net>
Subject: Code freeze on lite patches and schedule for submission into mainline kernel
Date: Wed, 3 Mar 2004 13:54:10 +0530 [thread overview]
Message-ID: <200403031354.10370.amitkale@emsyssoft.com> (raw)
Hi,
We have two sets of kgdb patches as of now: [core-lite, i386-lite, 8250] and
[core, i386, ppc, x86_64, eth]. First set of kgdb patches (lite) is fairly
clean. Let's consider it to be a candicate for submission to mainline kernel.
I am freezing the lite patches wrt. feature updates. Only bug-fixes and code
cleanups will be allowed in lite patches. You can make any feature
enhancements to second set of patches.
I propose following schedule for pushing kgdb lite into mainline kernel:
Take 1: 8th , Take 2: 15th, Take 3: 22nd, Take 4:29th. I'll download the
kernel snapshot (http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/) on
these dates and submit a single patch for possible acceptance into mainline
kenrel and feedback from community. Hopefully we'll succeed by end of this
month.
Please checkin any fixes or cleanups by end of this week. I plan to add some
documentation to core-lite.patch this week (will send it for review in a
separate email)
Comments/suggestions?
--
Amit Kale
EmSysSoft (http://www.emsyssoft.com)
KGDB: Linux Kernel Source Level Debugger (http://kgdb.sourceforge.net)
next reply other threads:[~2004-03-03 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 8:24 Amit S. Kale [this message]
2004-03-03 10:56 ` Code freeze on lite patches and schedule for submission into mainline kernel Pavel Machek
2004-03-03 11:17 ` Amit S. Kale
2004-03-03 11:01 ` Pavel Machek
2004-03-03 11:16 ` Amit S. Kale
2004-03-03 11:22 ` Pavel Machek
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=200403031354.10370.amitkale@emsyssoft.com \
--to=amitkale@emsyssoft.com \
--cc=george@mvista.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=trini@kernel.crashing.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).