All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Tom Rini <trini@kernel.crashing.org>
Cc: akpm@osdl.org, george@mvista.com, amitkale@emsyssoft.com,
	Andi Kleen <ak@suse.de>,
	jim.houston@comcast.net,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: BitKeeper repo for KGDB
Date: Wed, 28 Jan 2004 18:44:02 +0100	[thread overview]
Message-ID: <20040128174402.GI340@elf.ucw.cz> (raw)
In-Reply-To: <20040128170520.GI6577@stop.crashing.org>

Hi!

> > > Hello everybody.  Since I've been talking with George off-list about
> > > trying to merge the various versions of KGDB around, and I just read the
> > > thread between Andy and Jim about conflicting on KGDB work, I've put up
> > > a BitKeeper repository[1] to try and coordinate things.
> > > 
> > > What's in there right now is Amit's kgdb 2.1.0, without the ethernet
> > > patch.   There's also all of the changes for PPC and for generic stuffs
> > > that I've been doing of late.
> > > 
> > > What I'll be doing shortly (this afternoon even) is to change from a
> > > struct of function pointers, for the arch specific functions, into a set
> > > of provided, weak, variants and then allow arches to override as needed.
> > > 
> > > What I'd like is for someone to move the ethernet bits from the -mm tree
> > > into here, and for people to merge the fixes / enhancements that're in
> > > their per-arch stubs in the -mm tree into the split design that Amit's
> > > version has.
> > > 
> > > Comments? Screams? Patches? :)
> > 
> > This one. It compiles. It needs -netpoll. It probably does not work.
> 
> Er, what's this against?  I don't have drivers/net/kgdb_eth.c in my repo
> right now (nor the -netpoll patch, but I'll happily take a patch to add
> the kgdb over enet stub and -netpoll).

It's against 2.6 + -netpoll + Amit's patch.
								Pavel
-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

  reply	other threads:[~2004-01-28 17:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-27 18:40 BitKeeper repo for KGDB Tom Rini
2004-01-27 19:31 ` Sam Ravnborg
2004-01-27 19:46   ` Dave Jones
2004-01-27 20:07 ` Chris Wright
2004-01-27 21:02   ` Tom Rini
2004-01-28  9:50     ` Dave Jones
2004-01-28 16:51 ` Pavel Machek
2004-01-28 17:05   ` Tom Rini
2004-01-28 17:44     ` Pavel Machek [this message]
2004-01-28 17:56       ` Tom Rini
2004-01-28 18:04         ` Pavel Machek
2004-02-06 22:35         ` Tom Rini
2004-02-06 22:55           ` Pavel Machek
2004-02-06 23:02             ` Tom Rini
2004-02-09  1:29               ` Matt Mackall
2004-02-09 15:50                 ` Tom Rini
2004-02-09 17:38                   ` Matt Mackall
2004-02-10  7:57                     ` Amit S. Kale
2004-02-10  8:27                       ` Amit S. Kale
2004-02-10 19:26                         ` Tom Rini
2004-02-11 14:35                           ` Amit S. Kale
2004-02-10  8:46                       ` Dave Jones
2004-02-10 19:22                         ` Tom Rini
2004-02-10 19:23                           ` Dave Jones
2004-01-30 18:18 ` 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=20040128174402.GI340@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=amitkale@emsyssoft.com \
    --cc=george@mvista.com \
    --cc=jim.houston@comcast.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 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.