From: Pavel Machek <pavel@ucw.cz>
To: Tom Rini <trini@kernel.crashing.org>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][6/6] A different KGDB stub
Date: Wed, 18 Feb 2004 00:08:55 +0100 [thread overview]
Message-ID: <20040217230855.GB1560@elf.ucw.cz> (raw)
In-Reply-To: <20040217223817.GJ16881@smtp.west.cox.net>
Hi!
> > > The following is the x86_64-specific bits to this KGDB stub (Pavel, can
> > > you give this a try please? Thanks).
> >
> > I can only see [0/6],[1/6] and [6/6] on l-k. Could you perhaps mail me
> > complete diff against 2.6.2 to try? [Or against some other version I
> > can get from kernel.org...)
>
> I'll blame the slow mailserver and hope they all get through
> eventually.
Yes, now only #2 is missing :-))).
> The following is the patch before I split it up. Against 2.6.3-rc4 +
> bk-netdev from 2.6.3-rc3-mm1 (otherwise kgdboe won't work at all):
I'll try without kgdboe, first.
I'm getting some compile errors, stay tuned.
Meanwhile: [and taking this public]
arch/x86_64/kernel/x86_64-stub.c: this is really horrible name for a
file. Can we have arch/x86_64/kernel/kgdb.c? or kgdb-stub.c at worst..
also kernel/kgdb.c sounds better than kernel/kgdbstub.c.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-02-17 23:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 22:04 Tom Rini
[not found] ` <20040217223040.GA1560@elf.ucw.cz>
[not found] ` <20040217223817.GJ16881@smtp.west.cox.net>
2004-02-17 23:08 ` Pavel Machek [this message]
2004-02-17 23:13 ` Tom Rini
[not found] <20040212000408.GG19676@smtp.west.cox.net.suse.lists.linux.kernel>
2004-02-12 6:43 ` Andi Kleen
2004-02-12 15:50 ` Tom Rini
2004-02-13 3:00 ` Andi Kleen
2004-02-12 16:27 ` Tom Rini
2004-02-16 19:47 ` Pavel Machek
2004-02-12 18:32 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2004-02-12 0:04 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=20040217230855.GB1560@elf.ucw.cz \
--to=pavel@ucw.cz \
--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®