On Fri, 16 Nov 2007 19:46:36 -0800 Pete/Piet Delaney wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Lance Spaulding wrote: > > Hi all, > > > > Can someone tell me how to download the kgdb patches for the 2.6.23 > > kernel? I believe they are at: > > > > http://git.kernel.org/?p=linux/kernel/git/jwessel/linux-2.6-kgdb.git;a=shortlog;h=kgdb_2.6.23 > > > > but I'm not sure how to check them out. I tried clicking 'snapshot' by > > each patch to download them but the .gz files that it downloads appear > > corrupt (gunzip fails to uncompres them). Anyway can someone tell me > > how to check them out using git and what order to apply them? > > I don't think you can. Jason's branch is in preparation for Andrew's > mm patch series which is off a rc update. What holding up getting the > kgdb patch push from mm to Linus's kernel? > > I'm currently catching up on 2.6.12 to 2.6.16 and will upgrade to 2.6.22 > most likely next. Getting the kgdb patch into the mainstream would save > developers a lot a time messing with this. Jason just published the > kgdb patch for going into the mainline on 10/15/2007 (Yesterday). > > I think it might be worth while to make clones of Greg Kroah-Hartman's > stable repositories and merge Jason's patches back into those > repos and make them git down loadable from git.kernel.org. Looks > like Andrew thinks it's too soon to go into the mainstream and > it has to be reviewed even more and will go into 2.6.25. > > Perhaps it would have be better to make the kgdb patches for > Andrew based off the current stable release and then pull > those changes to a mm branch. Back porting from mm back to > the stable releases double the effort. > > Maybe while Jason is pushing to get the kgdb patch into the > mainstream we can backport his changes to the stable branches > and make them available like Greg Kroah-Hartman's git repositories. > With 2.6.16.x being an important repo that I'm syncing with maybe > I can post an git repo for that. If Jason has time to backport his > branches back to stable repos that would be great but I suspect > he may busy enough with "just" the push to the mainstream for > 2.6.25 and the mm series. > > Having a kgdb git repo for each of the -stable trees would be ideal. > Looks like 2.6.22 will be the next important stable .x kernel tree.
Another option that you can try is to take the 2.6.23-mm1 kgdb patches and merge them into 2.6.23. There are a few minor rejects when they are merged, but I just tried this and they were very easy to fix. The 2.6.23-mm1 patches are here (not as one large patch file, but as "broken-out" patch files): http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23/2.6.23-mm1/broken-out/ and the patch-series (tells the order that the patches were applied) is here: http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23/2.6.23-mm1/patch-series so you can see in patch-series that the kgdb patches are applied in this order: git-kgdb.patch git-kgdb-fixup.patch git-kgdb-be-modern.patch disable-kgdb-on-ppc.patch It builds with KGDB enabled. Not run-tested. HTH. --- ~Randy ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Kgdb-bugreport mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
