Re: [PATCH][0/6] A different KGDB stub

[Pavel Machek]

Hi!

> > > > The following is my next attempt at a different KGDB stub
> > > > for your tree
> > >
> > > Is this the patch which everyone agrees on?
> >
> > It is based on Amit's version, so I think answer is "yes". I certainly
> > like this one.
> 
> I don't agree. I did a few more cleanups after Andi expressed concerns over 
> globals kgdb_memerr and debugger_memerr_expected.
> 
> I liked Pavel's approach. Let's first get a minimal kgdb stub into mainline 
> kernel. Even this much is going to involve some effort. We can merge other 
> features later.
> 
> Let's create a cvs tree at kgdb.sourceforge.net for kgdb components to be 
> pushed int mainline kernel. This split is to keep current kgdb unaffected. 
> People who are already using it won't be affected.

I do not think we want separate CVS tree.

What about simply splitting core.patch into core-lite.patch and
core.patch, maybe do the same with i386 patch, and be done with that?
[We do not have enough people for a fork, I think].

Hopefully soon after that *-lite is merged, so it disappears, and
stuff is easy once again.
									Pavel
-- 
Horseback riding is like software...
...vgf orggre jura vgf serr.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/