From: Pavel Machek <pavel@suse.cz>
To: Tom Rini <trini@kernel.crashing.org>
Cc: "Amit S. Kale" <amitkale@emsyssoft.com>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Split kgdb into "lite" and "normal" parts
Date: Wed, 25 Feb 2004 00:27:03 +0100 [thread overview]
Message-ID: <20040224232703.GC9209@elf.ucw.cz> (raw)
In-Reply-To: <20040224232137.GJ1052@smtp.west.cox.net>
Hi!
> > > > Tested (core-lite.patch + i386-lite.patch + 8250.patch) combination.
> > > > Looks good.
> > > >
> > > > Let's first check this in and then do more cleanups.
> > > > Tom, does it sound ok?
> > >
> > > This sounds fine to me. Pavel, I'm guessing you did this with quilt,
> > > could you provide some pointers on how to replicate this in the future?
> >
> > Unfortunately, I done it by hand :-(. But if -lite parts are not
> > merged, soon, I'll be forced to start using quilt. Doing stuff by hand
> > is quite painfull...
>
> There's still a whole bunch of bogons in the -lite patch still, so I
> don't think it should be merged yet.
Well, it seems to contains a *lot* less bogons than what currently is
in -mm series.
What big problems do you see? It does not yet use weak symbols, but I
do not think that's a serious problem. What else?
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-02-24 23:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 22:50 Split kgdb into "lite" and "normal" parts Pavel Machek
2004-02-19 7:52 ` Amit S. Kale
2004-02-24 21:39 ` Tom Rini
2004-02-24 22:15 ` Pavel Machek
2004-02-24 23:21 ` Tom Rini
2004-02-24 23:27 ` Pavel Machek [this message]
2004-02-24 23:38 ` Tom Rini
2004-02-24 23:49 ` Pavel Machek
2004-02-24 23:57 ` Tom Rini
2004-02-25 0:08 ` Pavel Machek
2004-02-25 7:15 ` Amit S. Kale
2004-02-25 7:19 ` Amit S. Kale
2004-02-25 15:58 ` Tom Rini
2004-02-25 20:58 ` Tom Rini
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=20040224232703.GC9209@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=amitkale@emsyssoft.com \
--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 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.