From: Pavel Machek <pavel@ucw.cz>
To: "Amit S. Kale" <amitkale@emsyssoft.com>
Cc: Tom Rini <trini@kernel.crashing.org>,
George Anzinger <george@mvista.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
KGDB bugreports <kgdb-bugreport@lists.sourceforge.net>
Subject: Re: Code freeze on lite patches and schedule for submission into mainline kernel
Date: Wed, 3 Mar 2004 12:22:16 +0100 [thread overview]
Message-ID: <20040303112216.GD342@elf.ucw.cz> (raw)
In-Reply-To: <200403031646.22151.amitkale@emsyssoft.com>
> > > 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.
> >
> > There may be better way to get kgdb into mainline.
> >
> > AFAICS, mainline already contains kgdb/ppc. Submiting "core-lite,
> > ppc-lite, 8250" would then be simply much needed cleanup. We can push
> > i386 few days after that.
>
> ppc.patch removes arch/ppc/kernel/ppc-stub.c and adds a new file kgdb.c I
> think that has a greater rejection chance.
>
> Let's not change the direction now. Some time ago there was another view that
> x86_64 would be easier. We have already had sufficient headache because of
> split -lite -heavy patches. Let's try to finish that asap.
Okay, you are right. i386 is best tested.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
prev parent reply other threads:[~2004-03-03 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 8:24 Amit S. Kale
2004-03-03 10:56 ` 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 [this message]
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=20040303112216.GD342@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=amitkale@emsyssoft.com \
--cc=george@mvista.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®