public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Amit S. Kale" <amitkale@linsyssoft.com>
To: Tom Rini <trini@kernel.crashing.org>, Robert Picco <Robert.Picco@hp.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org,
	kgdb-bugreport@lists.sourceforge.net
Subject: Re: [Kgdb-bugreport] Re: 2.6.6-mm3
Date: Tue, 18 May 2004 19:15:34 +0530	[thread overview]
Message-ID: <200405181915.34077.amitkale@linsyssoft.com> (raw)
In-Reply-To: <20040517175642.GL6763@smtp.west.cox.net>

On Monday 17 May 2004 11:26 pm, Tom Rini wrote:
> On Mon, May 17, 2004 at 09:38:13AM -0700, Tom Rini wrote:
> > On Mon, May 17, 2004 at 12:30:25PM -0400, Robert Picco wrote:
> > > Tom Rini wrote:
> > > >On Sun, May 16, 2004 at 02:55:14AM -0700, Andrew Morton wrote:
> > > >>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6/2
> > > >>.6.6-mm3/
> > > >>
> > > >>- A few VM changes, getting things synced up better with Andrea's
> > > >> work.
> > > >>
> > > >>- A new kgdb stub, for ia64 (what happened to the grand unified kgdb
> > > >> project?)
> > > >
> > > >No one asked the ia64 folks who did that work "Hey, have you looked at
> > > >the grand unified kgdb project on kgdb.sf.net ?" would be my guess.
> > > >
> > > >Having said that, if you're willing to go with a slightly late
> > > >initalizing (I saw part of the early_param work get dropped again I
> > > >think, so I'm gonna guess you don't wanna deal with that again yet)
> > > > KGDB for i386 and PPC32, I can whip something up vs 2.6.6 in a day or
> > > > so.
> > >
> > > I did the ia64 port and started with Andrew's 2.6.4-mm2 i386 sources.
> > > I'm assuming the long term strategy is to move to a unified kgdb being
> > > done on sourceforge?  If so, I'll take a look at this.
> >
> > My long term strategy is to get everyone using the version on
> > sourceforge that splits out the common portions of the stub from the
> > arch-specific portions.  If you could go ahead and get ia64 working on
> > this as well I'd appreciate it.
> >
> > Right now it's still vs 2.6.5, but I'm going to try and fix that today
> > or tomorrow to be vs 2.6.6.
>
> OK, I've updated things to 2.6.6.

That's great! Thanks.
-Amit


  reply	other threads:[~2004-05-18 13:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-16  9:55 2.6.6-mm3 Andrew Morton
2004-05-16 10:35 ` 2.6.6-mm3 Prakash K. Cheemplavam
2004-05-16 11:00   ` 2.6.6-mm3 Gene Heskett
2004-05-16 16:29   ` 2.6.6-mm3 Andrew Morton
2004-05-16 18:38 ` 2.6.6-mm3: USB console.c doesn't compile Adrian Bunk
2004-05-17 16:32   ` Greg KH
2004-05-16 20:15 ` [patch] 2.6.6-mm3: more PC9800 removal Adrian Bunk
2004-05-16 20:35 ` [patch] 2.6.6-mm3: remove PC9800 from should-fix Adrian Bunk
2004-05-17 11:52 ` 2.6.6-mm3 Eric W. Biederman
2004-05-17 12:57 ` 2.6.6-mm3 Aristeu Sergio Rozanski Filho
2004-05-17 15:06   ` 2.6.6-mm3 Robert Picco
2004-05-17 15:51     ` 2.6.6-mm3 Aristeu Sergio Rozanski Filho
2004-05-17 13:09 ` Scroll wheel on PS/2 Logitech MouseMan Wheel no longer works (was Re: 2.6.6-mm3) Sean Neakums
2004-05-17 18:10   ` Dmitry Torokhov
     [not found]     ` <6u4qqejiny.fsf@zork.zork.net>
     [not found]       ` <200405191256.32335.dtor_core@ameritech.net>
2004-05-20  7:49         ` Sean Neakums
2004-05-26  3:40           ` Dmitry Torokhov
2004-06-06 17:49             ` Vojtech Pavlik
2004-05-17 16:14 ` 2.6.6-mm3 Tom Rini
2004-05-17 16:30   ` 2.6.6-mm3 Robert Picco
2004-05-17 16:38     ` 2.6.6-mm3 Tom Rini
2004-05-17 17:56       ` 2.6.6-mm3 Tom Rini
2004-05-18 13:45         ` Amit S. Kale [this message]
2004-05-17 17:20 ` 2.6.6-mm3 Chris Wright
2004-05-17 17:42 ` [PATCH][PPC32] Update Motorola LoPEC and Sandpoint defconfigs Tom Rini
2004-05-17 17:54   ` [PATCH][PPC32] Remove 'mem_pieces_append' Tom Rini
2004-05-17 18:06     ` [PATCH][PPC32] Some fixes for 'make O=...' Tom Rini
2004-05-18  2:08 ` 2.6.6-mm3: i810 agpgart module can't be initialized Clemens Schwaighofer

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=200405181915.34077.amitkale@linsyssoft.com \
    --to=amitkale@linsyssoft.com \
    --cc=Robert.Picco@hp.com \
    --cc=akpm@osdl.org \
    --cc=kgdb-bugreport@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox