On Tue, 2015-01-06 at 18:54 +0000, Daniel Thompson wrote: > Hi Jason > > I'm trying to figure out what to do with my long-outstanding kgdb/kdb > patches in preparation for the 3.20 merge window. > > As of now I have five pending patch sets some of which are well over six > months old (and none have nay outstanding review comments). > > When I raised this with you a couple of months ago, two of the patch > sets did land in your kgdb-next tree. However nothing seems to have > happened since then and I couldn't find any messages from you during the > 3.19 merge window. > > I'm afraid I don't know what else I need to do to progress things. > > I do plan to do routine rebasing and resending of my patchsets but, > based on the past experience, that seems unlikely to be enough to get > the code delivered in 3.20. > > Do you think I would be better sending these patches via someone else? > In any case, advice would be very welcome.
Andrew? I think Daniel's kgdb patches are bug fixes. Can you please pick them up? ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. www.gigenet.com _______________________________________________ Kgdb-bugreport mailing list Kgdb-bugreport@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
